procyberian/emacs
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Emphasize that GPG passphrase caching is temporary (Bug#29907)

Browse source 
* doc/misc/epa.texi (Caching Passphrases): Clarify that caching is
temporary.
(GnuPG version compatibility): Fix typo.
This commit is contained in:
Noam Postavsky 2018-01-28 12:34:51 -05:00
parent 4b5711b2b2
commit 9e6889c65a
1 changed files with 4 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

6
doc/misc/epa.texi
View file

@ -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