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 20:59:10 +0900 Message-ID: <87pqlwkfw1.fsf-ueno@unixuser.org> 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> <87mxh0sy9o.fsf@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1309351597 11322 80.91.229.12 (29 Jun 2011 12:46:37 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 29 Jun 2011 12:46:37 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jun 29 14:46:33 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 1QbuA5-00018N-CF for ged-emacs-devel@m.gmane.org; Wed, 29 Jun 2011 14:46:33 +0200 Original-Received: from localhost ([::1]:38305 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QbuA4-0000IK-6k for ged-emacs-devel@m.gmane.org; Wed, 29 Jun 2011 08:46:32 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:54340) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QbtQP-0004q9-LU for emacs-devel@gnu.org; Wed, 29 Jun 2011 07:59:22 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QbtQN-0007FP-VQ for emacs-devel@gnu.org; Wed, 29 Jun 2011 07:59:21 -0400 Original-Received: from ivory4.scn-net.ne.jp ([219.117.176.192]:42021) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1QbtQN-0007FH-7y for emacs-devel@gnu.org; Wed, 29 Jun 2011 07:59:19 -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 20:59:12 +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 p5TBxBut018415 for ; Wed, 29 Jun 2011 20:59:12 +0900 In-Reply-To: <87mxh0sy9o.fsf@lifelogs.com> (Ted Zlatanov's message of "Wed, 29 Jun 2011 05:54:59 -0500") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (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:141169 Archived-At: Ted Zlatanov writes: > I would appreciate it if you were more specific about "does not work" by > either filing a bug or explaining. Obviously it works for me and Lars, > who tested it. Similarly, since you wrote EPA/EPG, your advice on > reducing complexity when we use it is greatly appreciated but you don't > give us any here. I have too many minor comments to list here, but at least duplicate code regarding stashfile should be simplified by supplying a custom passphrase-callback and calling epg-{encrypt,decrypt}-string. Currently it's really hard to understand what the code does. > DU> I don't want to see that the Gnus password-caching feature becomes > DU> harder and harder to use daily... > > I don't think we've done anything that makes it harder to use. The GPG > token functionality is off by default right now. Yes, and I hope that it won't be on by default. > So it's not line-based. I think that's a minus: people expect to be > able to copy a line out of the netrc file, and it makes managing such > files easier. I think typical users don't want to edit the auto-saved passwords file itself, as long as it saves their passwords and serves it to services as needed. Regards, -- Daiki Ueno