From: Noam Postavsky Date: Sun, 28 Jan 2018 17:34:51 +0000 (-0500) Subject: Emphasize that GPG passphrase caching is temporary (Bug#29907) X-Git-Tag: emacs-26.1-rc1~286 X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=9e6889c65af15b80db3f19064a765c1d3a198b87;p=emacs.git Emphasize that GPG passphrase caching is temporary (Bug#29907) * doc/misc/epa.texi (Caching Passphrases): Clarify that caching is temporary. (GnuPG version compatibility): Fix typo. --- diff --git a/doc/misc/epa.texi b/doc/misc/epa.texi index 80ea43e8032..8c21a262a1e 100644 --- a/doc/misc/epa.texi +++ b/doc/misc/epa.texi @@ -455,7 +455,7 @@ GnuPG 2.1 uses a fixed address for the Unix domain socket used to communicate with gpg-agent. The @code{GPG_AGENT_INFO} environment variable, which is used by GnuPG 2.0 and 1.4, is ignored. That means, if your system has both GnuPG 2.1 and 1.4, the gpg command from GnuPG -1.4 is not able to use gpg-agent provided by 2.1 (at least out of box).q +1.4 is not able to use gpg-agent provided by 2.1 (at least out of box). @item GnuPG 2.1 (2.1.5 or later) has a mechanism to direct the Pinentry @@ -474,7 +474,9 @@ graphical prompt. Typing passphrases is a troublesome task if you frequently open and close the same file. GnuPG and EasyPG Assistant provide mechanisms to -remember your passphrases. However, the configuration is a bit +remember your passphrases for a limited time. Using these, you only +need to re-enter the passphrase occasionally. +However, the configuration is a bit confusing since it depends on your GnuPG installation@xref{GnuPG version compatibility}, encryption method (symmetric or public key), and whether or not you want to use gpg-agent. Here are some