summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorThien-Thi Nguyen <ttn@gnuvola.org>2021-04-07 03:20:24 -0400
committerThien-Thi Nguyen <ttn@gnuvola.org>2021-04-07 03:20:24 -0400
commitc8f07b0d743a8cbc065c4672e83b1e6c43c0249c (patch)
treed95582ccc66ca6eb7b91a6b6b94627cf7c7e26d5
parent7188d2b17aa5971fe7f3928fda6fa4541fe7b9bb (diff)
downloaddocs-c8f07b0d743a8cbc065c4672e83b1e6c43c0249c.tar.gz
docs-c8f07b0d743a8cbc065c4672e83b1e6c43c0249c.tar.bz2
docs-c8f07b0d743a8cbc065c4672e83b1e6c43c0249c.zip
add comma
-rw-r--r--anastasis.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/anastasis.rst b/anastasis.rst
index 17ce4d49..8d6b2fb7 100644
--- a/anastasis.rst
+++ b/anastasis.rst
@@ -165,7 +165,7 @@ Verification
For users to authorize "policy" operations we need an EdDSA key pair. As we
cannot assure that the corresponding private key is truly secret, such policy
operations must never be destructive: Should an adversary learn the private
-key, they could access (and with the **kdf_id** decrypt) the user's policy (but
+key, they could access (and with the **kdf_id**, decrypt) the user's policy (but
not the core secret), or upload a new version of the
**encrypted recovery document** (but not delete an existing version).