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

Clarify GnuPG version compatibility chapter

Browse source 
* doc/misc/epa.texi (GnuPG version compatibility): Make the gpg-agent
description a bit clearer.
This commit is contained in:
Daiki Ueno 2016-02-22 10:40:42 +09:00
parent 5e34c3671a
commit 2667b3ebae
1 changed files with 15 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

26
doc/misc/epa.texi
View file

@ -441,26 +441,30 @@ The default value is @code{t}.
@chapter GnuPG version compatibility @chapter GnuPG version compatibility
As of February 2016, there are three active branches of GnuPG: 2.1, As of February 2016, there are three active branches of GnuPG: 2.1,
2.0, and 1.4. All those branches should work flawlessly with Emacs, 2.0, and 1.4. All those branches should work flawlessly with Emacs
with basic use-cases. They have, however, some incompatible with basic use-cases. They have, however, some incompatible
characteristics, which might be visible when used from Emacs. characteristics, which might be visible when used from Emacs.
@itemize @itemize
@item @item
The key store format used by 2.1 is incompatible with 1.4. That The key store format used by GnuPG 2.1 is incompatible with 1.4. That
means, a key created with 2.1 might not be visible with 1.4. means, a key created with GnuPG 2.1 is not visible with 1.4.
@item @item
2.1 uses a fixed Unix domain socket for gpg-agent, and ignores the GnuPG 2.1 uses a fixed address for the Unix domain socket used to
@code{GPG_AGENT_INFO} environment variable, used by 2.0 and 1.4. 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
@item @item
2.1 (2.1.5 or later) has a mechanism to direct the Pinentry password GnuPG 2.1 (2.1.5 or later) has a mechanism to direct the Pinentry
prompt to the Emacs minibuffer@footnote{To enable this feature, add password prompt to the Emacs minibuffer@footnote{To enable this
@samp{allow-emacs-pinentry} to @file{~/.gnupg/gpg-agent.conf} and let feature, add @samp{allow-emacs-pinentry} to
gpg-agent reload the configuration, with: @samp{gpgconf --reload gpg-agent}}, @file{~/.gnupg/gpg-agent.conf} and let gpg-agent reload the
which would be useful when you use Emacs remotely or from a text-only configuration, with: @samp{gpgconf --reload gpg-agent}}, which would
terminal. That feature is not available in other versions, and more be useful when you use Emacs remotely or from a text-only terminal.
That feature is not available in other versions, and more
specifically, with 2.0 (as of 2.0.29), there is no way to avoid the specifically, with 2.0 (as of 2.0.29), there is no way to avoid the
graphical prompt. graphical prompt.
@end itemize @end itemize