aboutsummaryrefslogtreecommitdiffstats
path: root/doc/misc
diff options
context:
space:
mode:
authorDaiki Ueno2016-02-22 10:40:42 +0900
committerDaiki Ueno2016-02-22 10:46:35 +0900
commit2667b3ebaee4c7d136e8320d859c7385c7ff88e5 (patch)
treee99087ef402fc75daa36924546a439dc52079110 /doc/misc
parent5e34c3671a657ee4b0355d062e1412f1f009dbd0 (diff)
downloademacs-2667b3ebaee4c7d136e8320d859c7385c7ff88e5.tar.gz
emacs-2667b3ebaee4c7d136e8320d859c7385c7ff88e5.zip
Clarify GnuPG version compatibility chapter
* doc/misc/epa.texi (GnuPG version compatibility): Make the gpg-agent description a bit clearer.
Diffstat (limited to 'doc/misc')
-rw-r--r--doc/misc/epa.texi26
1 files changed, 15 insertions, 11 deletions
diff --git a/doc/misc/epa.texi b/doc/misc/epa.texi
index 4b7b11834b3..cb177c41f49 100644
--- a/doc/misc/epa.texi
+++ b/doc/misc/epa.texi
@@ -441,26 +441,30 @@ The default value is @code{t}.
441@chapter GnuPG version compatibility 441@chapter GnuPG version compatibility
442 442
443As of February 2016, there are three active branches of GnuPG: 2.1, 443As of February 2016, there are three active branches of GnuPG: 2.1,
4442.0, and 1.4. All those branches should work flawlessly with Emacs, 4442.0, and 1.4. All those branches should work flawlessly with Emacs
445with basic use-cases. They have, however, some incompatible 445with basic use-cases. They have, however, some incompatible
446characteristics, which might be visible when used from Emacs. 446characteristics, which might be visible when used from Emacs.
447 447
448@itemize 448@itemize
449@item 449@item
450The key store format used by 2.1 is incompatible with 1.4. That 450The key store format used by GnuPG 2.1 is incompatible with 1.4. That
451means, a key created with 2.1 might not be visible with 1.4. 451means, a key created with GnuPG 2.1 is not visible with 1.4.
452 452
453@item 453@item
4542.1 uses a fixed Unix domain socket for gpg-agent, and ignores the 454GnuPG 2.1 uses a fixed address for the Unix domain socket used to
455@code{GPG_AGENT_INFO} environment variable, used by 2.0 and 1.4. 455communicate with gpg-agent. The @code{GPG_AGENT_INFO} environment
456variable, which is used by GnuPG 2.0 and 1.4, is ignored. That means,
457if your system has both GnuPG 2.1 and 1.4, the gpg command from GnuPG
4581.4 is not able to use gpg-agent provided by 2.1 (at least out of box).q
456 459
457@item 460@item
4582.1 (2.1.5 or later) has a mechanism to direct the Pinentry password 461GnuPG 2.1 (2.1.5 or later) has a mechanism to direct the Pinentry
459prompt to the Emacs minibuffer@footnote{To enable this feature, add 462password prompt to the Emacs minibuffer@footnote{To enable this
460@samp{allow-emacs-pinentry} to @file{~/.gnupg/gpg-agent.conf} and let 463feature, add @samp{allow-emacs-pinentry} to
461gpg-agent reload the configuration, with: @samp{gpgconf --reload gpg-agent}}, 464@file{~/.gnupg/gpg-agent.conf} and let gpg-agent reload the
462which would be useful when you use Emacs remotely or from a text-only 465configuration, with: @samp{gpgconf --reload gpg-agent}}, which would
463terminal. That feature is not available in other versions, and more 466be useful when you use Emacs remotely or from a text-only terminal.
467That feature is not available in other versions, and more
464specifically, with 2.0 (as of 2.0.29), there is no way to avoid the 468specifically, with 2.0 (as of 2.0.29), there is no way to avoid the
465graphical prompt. 469graphical prompt.
466@end itemize 470@end itemize