From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.devel Subject: Re: bad epg.el+GPG2 behavior: unavoidable passphrase pinentry prompt Date: Wed, 02 Oct 2013 09:38:04 -0400 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <87haczvlmr.fsf@flea.lifelogs.com> References: <878uyg0yp1.fsf@flea.lifelogs.com> <878uyfzf1w.fsf@flea.lifelogs.com> <87bo389lw0.fsf-ueno@gnu.org> <87y56cufkt.fsf@flea.lifelogs.com> <87y56b96uk.fsf-ueno@gnu.org> Reply-To: emacs-devel@gnu.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1380721099 9690 80.91.229.3 (2 Oct 2013 13:38:19 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 2 Oct 2013 13:38:19 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Oct 02 15:38:22 2013 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1VRMdB-0001Pl-Be for ged-emacs-devel@m.gmane.org; Wed, 02 Oct 2013 15:38:21 +0200 Original-Received: from localhost ([::1]:36177 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VRMdB-0003sb-0D for ged-emacs-devel@m.gmane.org; Wed, 02 Oct 2013 09:38:21 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40696) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VRMd3-0003qz-Sh for emacs-devel@gnu.org; Wed, 02 Oct 2013 09:38:19 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VRMcy-0001C0-Ka for emacs-devel@gnu.org; Wed, 02 Oct 2013 09:38:13 -0400 Original-Received: from plane.gmane.org ([80.91.229.3]:34240) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VRMcy-0001Bq-Dm for emacs-devel@gnu.org; Wed, 02 Oct 2013 09:38:08 -0400 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1VRMcx-0001BM-4z for emacs-devel@gnu.org; Wed, 02 Oct 2013 15:38:07 +0200 Original-Received: from c-98-229-61-72.hsd1.ma.comcast.net ([98.229.61.72]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 02 Oct 2013 15:38:07 +0200 Original-Received: from tzz by c-98-229-61-72.hsd1.ma.comcast.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 02 Oct 2013 15:38:07 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Original-Lines: 41 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: c-98-229-61-72.hsd1.ma.comcast.net X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6; d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" Mail-Copies-To: never User-Agent: Gnus/5.130008 (Ma Gnus v0.8) Emacs/24.3.50 (gnu/linux) Cancel-Lock: sha1:2Lvg9O6wmRFfLr3EHzLeJDwZfd8= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:163806 Archived-At: On Wed, 02 Oct 2013 21:48:19 +0900 Daiki Ueno wrote: DU> Ted Zlatanov writes: >> On Wed, 02 Oct 2013 16:23:27 +0900 Daiki Ueno wrote: >> DU> Ted Zlatanov 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