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: secure plist store Date: Wed, 29 Jun 2011 18:05:36 +0900 Message-ID: References: <87tycamhmv.fsf@lifelogs.com> <87pqmxvfoh.fsf@lifelogs.com> <87sjrttwh8.fsf@lifelogs.com> <87wrh4b9h9.fsf@lifelogs.com> <87aae05l8p.fsf-ueno@unixuser.org> <87k4d4b66p.fsf@lifelogs.com> <87wrh0fh4g.fsf_-_@lifelogs.com> <87y60ncma8.fsf_-_@lifelogs.com> <87vcvrne02.fsf-ueno@unixuser.org> <87r56ep3sm.fsf@lifelogs.com> <874o39n171.fsf-ueno@unixuser.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1309338381 28003 80.91.229.12 (29 Jun 2011 09:06:21 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 29 Jun 2011 09:06:21 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jun 29 11:06:17 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Qbqit-0008V9-Df for ged-emacs-devel@m.gmane.org; Wed, 29 Jun 2011 11:06:15 +0200 Original-Received: from localhost ([::1]:38917 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qbqir-0005zc-P6 for ged-emacs-devel@m.gmane.org; Wed, 29 Jun 2011 05:06:13 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:38104) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QbqiX-0005yk-8d for emacs-devel@gnu.org; Wed, 29 Jun 2011 05:05:57 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QbqiS-0003Yk-PK for emacs-devel@gnu.org; Wed, 29 Jun 2011 05:05:53 -0400 Original-Received: from ivory4.scn-net.ne.jp ([219.117.176.192]:49224) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1QbqiR-0003YZ-UN for emacs-devel@gnu.org; Wed, 29 Jun 2011 05:05:48 -0400 Original-Received: from ([192.168.0.187]) (envelope sender: ) by ivory4.scn-net.ne.jp with Active!Hunter esmtp server; Wed, 29 Jun 2011 18:05:43 +0900 Original-Received: Received: from well-done.deisui.org (g187018.scn-net.ne.jp [202.83.187.18]) (authenticated) by blue17.scn-net.ne.jp (unknown) with ESMTP id p5T95hSY008997 for ; Wed, 29 Jun 2011 18:05:43 +0900 In-Reply-To: (Lars Magne Ingebrigtsen's message of "Wed, 29 Jun 2011 10:25:11 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) X-Received-From: 219.117.176.192 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:141159 Archived-At: Lars Magne Ingebrigtsen writes: >> I didn't notice that the field encryption code is already checked in. >> However, it does not work for me at all and looks too complicated - also >> it apparently does not benefit from GPG2 passphrase caching (see "(auth) >> GnuPG and EasyPG Assistant Configuration"). > > Can't it be altered to support passphrase caching? Not really - GPG2 passphrase caching is smarter than elisp level caching as it uses unique ID embedded in GPG data, so it allows user to share passphrases even among multiple Emacs processes. >> --8<---------------cut here---------------start------------->8--- >> (("baz" :secret-user t :host "baz.example.org") >> ("bar" :secret-user t :host "bar.example.org") >> ("foo" :host "foo.example.org" :port 80)) >> "-----BEGIN PGP MESSAGE----- >> Version: GnuPG v2.0.17 (GNU/Linux) >> >> jA0EAwMCXQZhP/0Se0DUyTQcC17GCo0CdT+RfFFskWp4aNYW/aOT/qbv24M1vPfx >> TFi9AR7iVc6qlg+9cA3f3buYBGvp >> =UEHH >> -----END PGP MESSAGE----- > > The nice thing about the netrc format is that people can edit it > themselves. This looks more fragile. The above format is tentative and could be improved. Anyway, as the encrypted fields in netrc is also not easily editable and given that the people editing netrc are kind of power user, how about making netrc files as fallback and read-only from Gnus? Regards, -- Daiki Ueno