From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Robert Pluim Newsgroups: gmane.emacs.devel Subject: Re: Opportunistic STARTTLS in smtpmail.el Date: Tue, 31 May 2011 09:11:03 +0200 Organization: not if I can help it Message-ID: References: <87d3kal0za.fsf@lifelogs.com> <874o5mky4o.fsf@lifelogs.com> <8762ptue8r.fsf@lifelogs.com> <87k4e8ucw3.fsf@lifelogs.com> <87liyofwxp.fsf@lifelogs.com> <874o5cfui5.fsf@lifelogs.com> <87liyndz5l.fsf@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1306825901 16777 80.91.229.12 (31 May 2011 07:11:41 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 31 May 2011 07:11:41 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue May 31 09:11:35 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 1QRJ6y-0004B6-B8 for ged-emacs-devel@m.gmane.org; Tue, 31 May 2011 09:11:32 +0200 Original-Received: from localhost ([::1]:36486 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QRJ6x-0007y7-Ny for ged-emacs-devel@m.gmane.org; Tue, 31 May 2011 03:11:31 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:51144) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QRJ6r-0007tY-A2 for emacs-devel@gnu.org; Tue, 31 May 2011 03:11:28 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QRJ6n-0000tB-HR for emacs-devel@gnu.org; Tue, 31 May 2011 03:11:25 -0400 Original-Received: from lo.gmane.org ([80.91.229.12]:37639) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QRJ6n-0000sq-5o for emacs-devel@gnu.org; Tue, 31 May 2011 03:11:21 -0400 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1QRJ6i-00044p-UJ for emacs-devel@gnu.org; Tue, 31 May 2011 09:11:16 +0200 Original-Received: from lns-bzn-49f-81-56-191-143.adsl.proxad.net ([81.56.191.143]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 31 May 2011 09:11:16 +0200 Original-Received: from rpluim by lns-bzn-49f-81-56-191-143.adsl.proxad.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 31 May 2011 09:11:16 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Original-Lines: 37 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: lns-bzn-49f-81-56-191-143.adsl.proxad.net Mail-Copies-To: never User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (cygwin) Cancel-Lock: sha1:iYYva5GTi1noGwiq+9hWvtAa0lQ= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 80.91.229.12 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:139937 Archived-At: Lars Magne Ingebrigtsen writes: > Here's my concrete suggestion for how auth-source would deal with this > stuff. > > The design requirements are: > > 1) if users want it, credentials should be encrypted > > 2) the credentials should be stored in a file that can be edited by > hand, if necessary > > 5) it should be possible to check whether credentials exist without > giving a password, even if the credentials are encrypted > > My solution to all this is to allow putting encrypted stuff into the > ~/.authinfo file. > > It's currently a one-credential-per-line file like this, and this would > still be perfectly valid: > > machine news.foo.org force yes port nntp login bar password zot > > However, if auth-info.el prompts somebody for a password, auth-info.el > will also prompt them for whether the credentials should be stored > encrypted. Could this be a tri-state question: yes/no/never? (I'd be in the never camp, but you'd need to store that response somewhere...) Actually, there would be two questions: - do you want to store? y/n/never - do you want to encrypt? y/n/never with the 'never' modes being per-entry. Robert