From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.devel Subject: Re: Opportunistic STARTTLS in smtpmail.el Date: Thu, 02 Jun 2011 08:09:11 -0500 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <8762oocrd4.fsf@lifelogs.com> References: <874o5cfui5.fsf@lifelogs.com> <87liyndz5l.fsf@lifelogs.com> <87y61nnpoq.fsf@lifelogs.com> <87fwnuacc5.fsf@lifelogs.com> <878vtmo081.fsf@lifelogs.com> <87tycamhmv.fsf@lifelogs.com> <87pqmxvfoh.fsf@lifelogs.com> <87sjrttwh8.fsf@lifelogs.com> Reply-To: emacs-devel@gnu.org NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1307020224 16477 80.91.229.12 (2 Jun 2011 13:10:24 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 2 Jun 2011 13:10:24 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jun 02 15:10:20 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 1QS7fI-0007xy-FE for ged-emacs-devel@m.gmane.org; Thu, 02 Jun 2011 15:10:20 +0200 Original-Received: from localhost ([::1]:55116 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QS7fH-0008Mn-AL for ged-emacs-devel@m.gmane.org; Thu, 02 Jun 2011 09:10:19 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:46060) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QS7eV-0008CC-DR for emacs-devel@gnu.org; Thu, 02 Jun 2011 09:09:33 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QS7eS-00036M-8d for emacs-devel@gnu.org; Thu, 02 Jun 2011 09:09:30 -0400 Original-Received: from lo.gmane.org ([80.91.229.12]:45537) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QS7eR-000353-LZ for emacs-devel@gnu.org; Thu, 02 Jun 2011 09:09:27 -0400 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1QS7eQ-0007U2-Hl for emacs-devel@gnu.org; Thu, 02 Jun 2011 15:09:26 +0200 Original-Received: from 38.98.147.130 ([38.98.147.130]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 02 Jun 2011 15:09:26 +0200 Original-Received: from tzz by 38.98.147.130 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 02 Jun 2011 15:09:26 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Original-Lines: 31 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: 38.98.147.130 X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6; d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" Mail-Copies-To: never User-Agent: Gnus/5.110018 (No Gnus v0.18) Emacs/24.0.50 (gnu/linux) Cancel-Lock: sha1:Cf32qynryXdTR6ORYbAlwO1SSj0= 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:140059 Archived-At: On Thu, 02 Jun 2011 01:09:36 -0300 Stefan Monnier wrote: >> From my perspective the chief benefit is that any `auth-source-search' >> call against an unencrypted file will not require a passphrase until the >> password is actually needed, and yet the password will be stored >> securely. SM> Sounds OK. But only if you push if further and deprecate SM> authinfo.gpg. On Thu, 02 Jun 2011 10:57:41 +0200 Robert Pluim wrote: RP> I'm not clear on why you'd want that. I can imagine someone wanting to RP> hide username & server identities from inspection, not just the RP> associated passwords. ie I distinguish 3 cases RP> 1) everything unencrypted RP> 2) passwords encrypted only RP> 3) everything encrypted It will be less necessary as the first `auth-sources' choice, but still useful, as Robert noted (I see case 2 as "encrypted tokens" since any token can be encrypted in my proposal). I'll simply make `auth-sources' ("~/.authinfo" "~/.authinfo.gpg") which as a default will work fine. Creation prompts will target the first one. The users can put insecure or token-encrypted data in the first one and use the second one for more secure storage. Ted