From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: bad epg.el+GPG2 behavior: unavoidable passphrase pinentry prompt
Date: Wed, 02 Oct 2013 09:38:04 -0400 [thread overview]
Message-ID: <87haczvlmr.fsf@flea.lifelogs.com> (raw)
In-Reply-To: 87y56b96uk.fsf-ueno@gnu.org
On Wed, 02 Oct 2013 21:48:19 +0900 Daiki Ueno <ueno@gnu.org> wrote:
DU> Ted Zlatanov <tzz@lifelogs.com> writes:
>> On Wed, 02 Oct 2013 16:23:27 +0900 Daiki Ueno <ueno@gnu.org> wrote:
>>
DU> Ted Zlatanov <tzz@lifelogs.com> writes:
>>>> 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?
>>
DU> Why don't you ask Werner directly about the ideas behind this, instead
DU> of complaining here and seeking for a workaround?
>>
>> Because the bug or misbehavior is specifically in epg.el and I don't
>> know the best way to fix it.
DU> Well, I didn't mean to attack you.
OK, I didn't take it that way :)
DU> I guess the configure option is disabled by default because it
DU> apparently has a security risk and there are not so many users of that
DU> feature. If you could provide a use case, that might help convince him
DU> to make --allow-loopback-pinentry enabled by default (and release 2.2
DU> and/or backport it to 2.0).
See my earlier e-mails. But my bigger concern is that for many users, a
new GnuPG release is years in the future, so even if you justify this
change, it won't help anyone quickly. IMHO epg.el should work around
this "feature" now with the --batch --passphrase-fd options that I
mentioned, especially if they can work on all GnuPG versions (I haven't
tested that).
My question now, since we understand the problem well, is if you agree
with this plan, and if so, do you need patches from me or other
contributors, or will you address it yourself? There's no urgency
implied here; I am simply trying to fix this for our users by the next
Emacs release.
Ted
next prev parent reply other threads:[~2013-10-02 13:38 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
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 [this message]
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=87haczvlmr.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.