summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKen Manheimer <ken.manheimer@gmail.com>2010-12-16 17:43:45 -0500
committerKen Manheimer <ken.manheimer@gmail.com>2010-12-16 17:43:45 -0500
commit0281bf138807e04b44b5891ec8d5a365dad8e3c1 (patch)
tree9c8dfd1d7d2aaa71780c4dff06856e84970c5893
parent075746e2c18959705ba7b186657fa84b01e42337 (diff)
downloademacs-0281bf138807e04b44b5891ec8d5a365dad8e3c1.tar.gz
(allout-mode), (allout-encrypt-string): Describe the problem with caching
of incorrect symmetric-decryption keys.
-rw-r--r--lisp/allout.el22
1 files changed, 15 insertions, 7 deletions
diff --git a/lisp/allout.el b/lisp/allout.el
index b67f8125a06..968c7081678 100644
--- a/lisp/allout.el
+++ b/lisp/allout.el
@@ -1920,12 +1920,12 @@ If the content of the topic containing the cursor was encrypted
for a save, it is automatically decrypted for continued editing.
PROBLEM: Attempting symmetric decryption with an incorrect key
-not only fails, but the incorrect key seems to be associated with
-the specific entry in the gpg cache, so that you do not get an
-opportunity to override the incorrect key and decrypt that
-entry. (Decryption of other entries is not affected.) To clear
-this problem, clear your gpg-agent's cache by sending it a '-HUP'
-signal.
+not only fails, but for some GnuPG v2 versions the incorrect key
+is apparently retained in the gpg cache and reused, preventing
+decryption, until the cache finally times out. That can take
+several minutes. \(Decryption of other entries is not affected.)
+To clear this problem before the cache times out, deliberately
+clear your gpg-agent's cache by sending it a '-HUP' signal.
See `allout-toggle-current-subtree-encryption' function docstring
and `allout-encrypt-unencrypted-on-saves' customization variable
@@ -6169,7 +6169,15 @@ dialog.
Optional REJECTED is for internal use, to convey the number of
rejections due to matches against
`allout-encryption-ciphertext-rejection-regexps', as limited by
-`allout-encryption-ciphertext-rejection-ceiling'."
+`allout-encryption-ciphertext-rejection-ceiling'.
+
+PROBLEM: Attempting symmetric decryption with an incorrect key
+not only fails, but for some GnuPG v2 versions the incorrect key
+is apparently retained in the gpg cache and reused, preventing
+decryption, until the cache finally times out. That can take
+several minutes. \(Decryption of other entries is not affected.)
+To clear this problem before the cache times out, deliberately
+clear your gpg-agent's cache by sending it a '-HUP' signal."
(require 'epg)
(require 'epa)