summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorThien-Thi Nguyen <ttn@gnuvola.org>2020-11-27 23:39:47 -0500
committerThien-Thi Nguyen <ttn@gnuvola.org>2020-11-27 23:39:47 -0500
commitaa72dd1c8bbcaf0a69a24d553681eaafd59140a9 (patch)
tree17a245cedffe15788538a6ddd2e7934b7cebf05a
parent563a699d4a62fee4c54f1c6c0ac6cea6b8642d41 (diff)
downloaddocs-aa72dd1c8bbcaf0a69a24d553681eaafd59140a9.tar.gz
docs-aa72dd1c8bbcaf0a69a24d553681eaafd59140a9.tar.bz2
docs-aa72dd1c8bbcaf0a69a24d553681eaafd59140a9.zip
mark up ‘kdf_id’
-rw-r--r--anastasis.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/anastasis.rst b/anastasis.rst
index f4f5538b..0e2a7b9c 100644
--- a/anastasis.rst
+++ b/anastasis.rst
@@ -162,7 +162,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).