From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Daiki Ueno Newsgroups: gmane.emacs.bugs Subject: bug#15552: 24.3.50; epa-file-cache-passphrase-for-symmetric-encryption not respected with GnuPG 2.x Date: Wed, 09 Oct 2013 12:53:14 +0900 Message-ID: References: <87r4bx0xsk.fsf@flea.lifelogs.com> <87fvscwswx.fsf-ueno-ueno@gnu.org> <87hacsutvp.fsf-ueno@gnu.org> <87fvsbctxe.fsf-ueno@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1381290846 4315 80.91.229.3 (9 Oct 2013 03:54:06 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 9 Oct 2013 03:54:06 +0000 (UTC) Cc: tzz@lifelogs.com, 15552@debbugs.gnu.org To: Stefan Monnier Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed Oct 09 05:54:10 2013 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1VTkqe-0006zL-I8 for geb-bug-gnu-emacs@m.gmane.org; Wed, 09 Oct 2013 05:54:08 +0200 Original-Received: from localhost ([::1]:40080 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VTkqe-0000Do-2J for geb-bug-gnu-emacs@m.gmane.org; Tue, 08 Oct 2013 23:54:08 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:46876) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VTkqa-0000Dj-AY for bug-gnu-emacs@gnu.org; Tue, 08 Oct 2013 23:54:05 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VTkqZ-00023T-A7 for bug-gnu-emacs@gnu.org; Tue, 08 Oct 2013 23:54:04 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:56343) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VTkqZ-00023P-6k for bug-gnu-emacs@gnu.org; Tue, 08 Oct 2013 23:54:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1VTkqY-0004HE-Hp for bug-gnu-emacs@gnu.org; Tue, 08 Oct 2013 23:54:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Daiki Ueno Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 09 Oct 2013 03:54:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 15552 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: notabug Original-Received: via spool by 15552-submit@debbugs.gnu.org id=B15552.138129080316392 (code B ref 15552); Wed, 09 Oct 2013 03:54:02 +0000 Original-Received: (at 15552) by debbugs.gnu.org; 9 Oct 2013 03:53:23 +0000 Original-Received: from localhost ([127.0.0.1]:36399 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1VTkpu-0004GJ-PS for submit@debbugs.gnu.org; Tue, 08 Oct 2013 23:53:23 -0400 Original-Received: from fencepost.gnu.org ([208.118.235.10]:43020) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1VTkps-0004GB-7J for 15552@debbugs.gnu.org; Tue, 08 Oct 2013 23:53:21 -0400 Original-Received: from du-a.org ([2001:e41:db5e:fb14::1]:38530 helo=localhost.localdomain) by fencepost.gnu.org with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1VTkpq-0002SK-Qt; Tue, 08 Oct 2013 23:53:19 -0400 In-Reply-To: (Stefan Monnier's message of "Tue, 08 Oct 2013 23:01:58 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:79075 Archived-At: Stefan Monnier writes: >> It used to work like that with gpg1. However, gpg2's implementation >> choice is that it does not leak the indication that gpg2 (actually >> gpg-agent) requires passphrase and it does not allow other tools than >> pinentry to inject passphrase. > > IOW epa-file-cache-passphrase-for-symmetric-encryption only works for > gpg1 and not for gpg2? s/works/has no effect/ >> IMO that's a good idea for security (as pinentry uses secmem). > > There are many situations where local security is not nearly as > important as convenience. But IIUC with gpg2 the general answer is "use > gpg-agent to do the caching", and it's supposed to work fine (i.e. it's > just as convenient as caching the password in Emacs). In this bug report, the reporter intentionally does not set up gpg-agent for his login session. Even the GnuPG 2.x manual spends one chapter on setting up gpg-agent before the chapter on gpg command itself. >>> Stefan "Also confused about what "symmetric" has to do with it" >> Perhaps you could try the above recipe under gpg-agent is properly set up: >> $ echo abc > file >> $ gpg --symmetric file >> $ eval `gpg-agent --daemon` >> $ gpg2 < file.gpg >> $ gpg2 < file.gpg >> You won't be asked for the passphrase at the second time, because >> gpg-agent remembers passphrase based on the file content. > > That doesn't really explain to me why > epa-file-cache-passphrase-for-symmetric-encryption has "symmetric" in > its name and more specifically why caching of passphrases would be > different for symmetric than for public key cryptography. I didn't get the question correctly, then. Look at the matrix of (info "(epa) Caching Passphrases"), check when a user is suggested to "set up elisp passphrase cache". Anyway, the name is not so important to me, as long as it discourages the use of the variable, so it could be e.g. epg-file-yo-mama-wears-fancy-glasses-detection-enabled. https://news.ycombinator.com/item?id=6372466