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: Thu, 03 Oct 2013 09:59:38 -0400 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <87bo36tpyt.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> <87haczvlmr.fsf@flea.lifelogs.com> 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 1380808806 30444 80.91.229.3 (3 Oct 2013 14:00:06 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 3 Oct 2013 14:00:06 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Oct 03 16:00:07 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 1VRjRh-0007GG-5w for ged-emacs-devel@m.gmane.org; Thu, 03 Oct 2013 16:00:01 +0200 Original-Received: from localhost ([::1]:43464 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VRjRd-00009W-QG for ged-emacs-devel@m.gmane.org; Thu, 03 Oct 2013 09:59:57 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:33823) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VRjRW-00008c-Gp for emacs-devel@gnu.org; Thu, 03 Oct 2013 09:59:55 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VRjRR-0004es-6V for emacs-devel@gnu.org; Thu, 03 Oct 2013 09:59:50 -0400 Original-Received: from plane.gmane.org ([80.91.229.3]:49015) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VRjRR-0004eY-0e for emacs-devel@gnu.org; Thu, 03 Oct 2013 09:59:45 -0400 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1VRjRO-000713-2r for emacs-devel@gnu.org; Thu, 03 Oct 2013 15:59:42 +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 ; Thu, 03 Oct 2013 15:59:42 +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 ; Thu, 03 Oct 2013 15:59:42 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Original-Lines: 33 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:t2rRqXcZ/sapzwxs2VkfrRKc5OQ= 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:163833 Archived-At: On Thu, 03 Oct 2013 10:52:46 +0900 Daiki Ueno wrote: DU> Ted Zlatanov writes: >> 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). DU> Well, that's a design decision not to use --batch here (and probably in DU> GPGME). If it used --batch, epg.el would need to know a passphrase even DU> if it is not needed (for example, it is already cached in gpg-agent, DU> encrypted with empty passphrase, etc.) And also it would inhibit gpg DU> from doing other user queries until the gpg command terminates. OK, so there's no way to avoid the broken behavior in epg.el and any fixes on the GnuPG side have to wait until a new release (and someone, possibly you, has to ask Werner for that fix). Is that accurate? It means we should recommend to Emacs users to use GnuPG 1.x if they want symmetric encryption to be usable (especially caching the passphrase). >> 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. DU> Please don't. Don't what? I asked several questions but am clearly waiting for your guidance. Ted