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: Wed, 01 Oct 2014 19:29:59 -0400 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <87k34jqsg8.fsf@lifelogs.com> References: <878ul1x4kw.fsf@uwakimon.sk.tsukuba.ac.jp> <87ppecv3pj.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 1412206199 26552 80.91.229.3 (1 Oct 2014 23:29:59 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 1 Oct 2014 23:29:59 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Oct 02 01:29:54 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 1XZTLF-0001rD-LQ for ged-emacs-devel@m.gmane.org; Thu, 02 Oct 2014 01:29:53 +0200 Original-Received: from localhost ([::1]:59258 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XZTLF-0000CN-2G for ged-emacs-devel@m.gmane.org; Wed, 01 Oct 2014 19:29:53 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:56605) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XZTKx-0000By-Tk for emacs-devel@gnu.org; Wed, 01 Oct 2014 19:29:41 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XZTKr-0003Rr-Bp for emacs-devel@gnu.org; Wed, 01 Oct 2014 19:29:35 -0400 Original-Received: from plane.gmane.org ([80.91.229.3]:49020) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XZTKr-0003Qu-5f for emacs-devel@gnu.org; Wed, 01 Oct 2014 19:29:29 -0400 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1XZTKn-0001hL-Bn for emacs-devel@gnu.org; Thu, 02 Oct 2014 01:29:25 +0200 Original-Received: from c-98-229-61-72.hsd1.ma.comcast.net ([98.229.61.72]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 02 Oct 2014 01:29:25 +0200 Original-Received: from tzz by c-98-229-61-72.hsd1.ma.comcast.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 02 Oct 2014 01:29:25 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Original-Lines: 23 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: c-98-229-61-72.hsd1.ma.comcast.net 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.130008 (Ma Gnus v0.8) Emacs/25.0.50 (gnu/linux) Cancel-Lock: sha1:369ci17I3dRIwRRA68+HffUhZaA= 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:174917 Archived-At: On Wed, 01 Oct 2014 16:02:12 +0200 Lars Magne Ingebrigtsen wrote: LMI> What I had planned on implementing was a way to make the user manage the LMI> security more explicitly. Here are the main options we need: ... LMI> It can all be done on the `open-network-stream' level. We discussed this before in several bug discussions. The GnuTLS errors (from an invalid certificate, for instance) happen at the C level and there are problems with trying to be interactive while reading from a network stream. See http://debbugs.gnu.org/cgi/bugreport.cgi?bug=11267, http://debbugs.gnu.org/cgi/bugreport.cgi?bug=15057, http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9017, http://debbugs.gnu.org/cgi/bugreport.cgi?bug=16784, and http://debbugs.gnu.org/cgi/bugreport.cgi?bug=16978 IIRC, the agreed-upon direction in http://debbugs.gnu.org/cgi/bugreport.cgi?bug=16978 was that we said the certificate UI was going to help the user manage certificate. And the errors from GnuTLS would point the user to that UI and tell them how to remedy the problem. And there would be magic dust and happy unicorns. Ted