From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: bad epg.el+GPG2 behavior: unavoidable passphrase pinentry prompt
Date: Sun, 29 Sep 2013 13:57:31 -0400 [thread overview]
Message-ID: <878uyfzf1w.fsf@flea.lifelogs.com> (raw)
In-Reply-To: m31u47ps53.fsf-ueno@gnu.org
On Sun, 29 Sep 2013 11:24:56 -0400 Daiki Ueno <ueno@gnu.org> wrote:
DU> Ted Zlatanov <tzz@lifelogs.com> writes:
>> It used to be possible to do
>>
>> GPG_AGENT_INFO=none gpg --decrypt foo.gpg
>> GPG_AGENT_INFO=none gpg --batch --decrypt foo.gpg
>> etc.
>>
>> but with GPG 2.x that seems to be disabled and the pinentry prompt pops
>> up no matter what. Without waiting for changes on the GPG side, the
>> only option seems to be to downgrade to GPG 1.x, which is not a great
>> solution. I haven't found a configuration option to disable the popup,
>> and even removing /usr/bin/pinentry and disabling the gpg-agent doesn't
>> work:
DU> Nowadays, GnuPG 2.1 or later has --pinentry-mode option, which provides
DU> a way to bypass the graphical pinentry prompt, like:
DU> $ gpg --batch --decrypt --pinetry-mode=loopback authinfo.gpg
DU> which just behaves like gpg1. I added the support to epg.el (see
DU> epg-pinentry-mode) some time ago, but not yet added any user option in
DU> epa.el.
DU> Patches (and testing) are welcome.
I'd love to test and patch, but the latest GnuPG release is 2.0.21 and I
can't find mentions of 2.1 on their website. 2.0.20 doesn't have the
--pinentry-mode option by default (tested in Gentoo). I assume this is
the relevant commit that introduces it:
http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commit;h=21feecd48f990b2569cb4b385dea3e57b9501525
It seems that GnuPG has to be explicitly compiled with
--allow-loopback-pinentry which IMO is a really painful requirement to
pass onto Emacs users. I am surprised by this, but perhaps I've
misunderstood something?
Ted
next prev parent reply other threads:[~2013-09-29 17:57 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-29 9:22 bad epg.el+GPG2 behavior: unavoidable passphrase pinentry prompt Ted Zlatanov
2013-09-29 15:07 ` Thierry Volpiatto
2013-09-29 17:48 ` Ted Zlatanov
2013-09-29 15:24 ` Daiki Ueno
2013-09-29 17:57 ` Ted Zlatanov [this message]
2013-10-02 7:23 ` Daiki Ueno
2013-10-02 10:34 ` Ted Zlatanov
2013-10-02 12:48 ` Daiki Ueno
2013-10-02 13:27 ` Andrey Kotlarski
2013-10-02 13:38 ` Ted Zlatanov
2013-10-03 1:52 ` Daiki Ueno
2013-10-03 13:59 ` Ted Zlatanov
2013-10-03 14:59 ` Stefan Monnier
2013-10-04 21:05 ` Ted Zlatanov
2013-10-05 16:21 ` Stefan Monnier
2013-10-07 18:15 ` Ted Zlatanov
2013-10-07 22:46 ` Stefan Monnier
2013-10-04 0:12 ` Daiki Ueno
2013-10-04 16:11 ` Ted Zlatanov
2013-09-30 18:53 ` Stefan Monnier
2013-09-30 19:24 ` Ted Zlatanov
2013-09-30 22:49 ` Stefan Monnier
2013-09-30 23:34 ` Ted Zlatanov
2013-10-01 0:40 ` Stefan Monnier
2013-10-01 1:13 ` Ted Zlatanov
2013-10-01 2:23 ` Stephen J. Turnbull
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878uyfzf1w.fsf@flea.lifelogs.com \
--to=tzz@lifelogs.com \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.