From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Daiki Ueno Newsgroups: gmane.emacs.devel Subject: Re: bad epg.el+GPG2 behavior: unavoidable passphrase pinentry prompt Date: Thu, 03 Oct 2013 10:52:46 +0900 Message-ID: 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> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1380765177 24121 80.91.229.3 (3 Oct 2013 01:52:57 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 3 Oct 2013 01:52:57 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Oct 03 03:53:01 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 1VRY68-0007on-SL for ged-emacs-devel@m.gmane.org; Thu, 03 Oct 2013 03:53:00 +0200 Original-Received: from localhost ([::1]:39463 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VRY68-0000Ik-Iv for ged-emacs-devel@m.gmane.org; Wed, 02 Oct 2013 21:53:00 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:38665) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VRY65-0000IR-Iz for emacs-devel@gnu.org; Wed, 02 Oct 2013 21:52:58 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VRY5z-0001RA-HU for emacs-devel@gnu.org; Wed, 02 Oct 2013 21:52:57 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:58846) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VRY5z-0001R6-Dm for emacs-devel@gnu.org; Wed, 02 Oct 2013 21:52:51 -0400 Original-Received: from du-a.org ([2001:e41:db5e:fb14::1]:37801 helo=localhost.localdomain) by fencepost.gnu.org with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1VRY5y-0005xA-7o for emacs-devel@gnu.org; Wed, 02 Oct 2013 21:52:50 -0400 In-Reply-To: <87haczvlmr.fsf@flea.lifelogs.com> (Ted Zlatanov's message of "Wed, 02 Oct 2013 09:38:04 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2001:4830:134:3::e 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:163819 Archived-At: 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). Well, that's a design decision not to use --batch here (and probably in GPGME). If it used --batch, epg.el would need to know a passphrase even if it is not needed (for example, it is already cached in gpg-agent, encrypted with empty passphrase, etc.) And also it would inhibit gpg from doing other user queries until the gpg command terminates. > 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. Please don't.