From b435c3b7ccab1caa36646c2ddc1f65f7fc3528e1 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Thu, 29 Aug 2013 14:32:25 -0400 Subject: clarify --- doc/design/encryption.mdwn | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'doc/design/encryption.mdwn') diff --git a/doc/design/encryption.mdwn b/doc/design/encryption.mdwn index 377de476e..cc0dd1684 100644 --- a/doc/design/encryption.mdwn +++ b/doc/design/encryption.mdwn @@ -107,8 +107,9 @@ A risk of this scheme is that, once the symmetric cipher has been obtained, it allows full access to all the encrypted content. Indeed anyone owning a key that used to be granted access could already have decrypted the cipher and stored a copy. While it is in possible to -revoke a key with `keyid-=`, it is designed for a -[[completely_different_purpose|encryption]]. +remove a key with `keyid-=`, it is designed for a +[[completely_different_purpose|/encryption]] and does not actually revoke +access. If git-annex stores the decrypted symmetric cipher in memory, then there is a risk that it could be intercepted from there by an attacker. Gpg -- cgit v1.2.3