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: POP3 password in plaintext? Date: Thu, 02 Oct 2014 13:04:15 -0400 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: References: <878ul1x4kw.fsf@uwakimon.sk.tsukuba.ac.jp> <87ppecv3pj.fsf@uwakimon.sk.tsukuba.ac.jp> <87bnpvutal.fsf@uwakimon.sk.tsukuba.ac.jp> Reply-To: emacs-devel@gnu.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1412269505 4164 80.91.229.3 (2 Oct 2014 17:05:05 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 2 Oct 2014 17:05:05 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Oct 02 19:04:58 2014 Return-path: Envelope-to: ged-emacs-devel@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 1XZjoI-0005J0-9Z for ged-emacs-devel@m.gmane.org; Thu, 02 Oct 2014 19:04:58 +0200 Original-Received: from localhost ([::1]:35316 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XZjoH-0007s2-TT for ged-emacs-devel@m.gmane.org; Thu, 02 Oct 2014 13:04:57 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:44012) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XZjny-0007q6-UN for emacs-devel@gnu.org; Thu, 02 Oct 2014 13:04:44 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XZjnr-0002cN-QH for emacs-devel@gnu.org; Thu, 02 Oct 2014 13:04:38 -0400 Original-Received: from plane.gmane.org ([80.91.229.3]:40458) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XZjnr-0002cF-K4 for emacs-devel@gnu.org; Thu, 02 Oct 2014 13:04:31 -0400 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1XZjno-00056e-VE for emacs-devel@gnu.org; Thu, 02 Oct 2014 19:04:28 +0200 Original-Received: from 198.0.146.153 ([198.0.146.153]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 02 Oct 2014 19:04:28 +0200 Original-Received: from tzz by 198.0.146.153 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 02 Oct 2014 19:04:28 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Original-Lines: 30 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 198.0.146.153 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.130012 (Ma Gnus v0.12) Emacs/24.4.50 (darwin) Cancel-Lock: sha1:1Rg9hbVLOChSWxeg6eg8DpXpXOE= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 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:174942 Archived-At: On Thu, 02 Oct 2014 10:58:10 +0900 "Stephen J. Turnbull" wrote: SJT> Ted Zlatanov writes: >> I think you mean `open-network-stream'? SJT> No, I really do mean "password-read". Mostly because not all SJT> protocols demand authentication immediately on opening a stream. Eg, SJT> many sites can be accessed with HTTP, will switch to HTTPS without SJT> authentication of the client, then present an HTML document for SJT> login. Clearly that's not possible, because the read password can be used at any point by the Lisp code; it's just data from that point on. Do you mean we should be able to send a password directly to a network or process stream at the C level? That makes a lot of sense to me and connects to the idea of "secret" data in the Emacs core. SJT> I think the self-signed cert manager should default to one-time-only SJT> or a short local expiration (1 hour? 1 day?) even if the cert is SJT> long-lived. Self-signature means that the server doesn't care to SJT> devote much financial resources to security (which may be correlated SJT> with carelessness concerning other security resources), and it's quite SJT> possible that some of those will be evil sites, recognized as such by SJT> user intuition, and I'd prefer to be warned about them on a second SJT> approach. That should be a user choice so yes it sounds reasonable, but no I don't think it should be the default. Ted