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: Network security manager Date: Tue, 18 Nov 2014 10:58:46 -0500 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <87oas4h555.fsf@lifelogs.com> References: <85a93pj1n5.fsf@stephe-leake.org> <87sihg7r73.fsf@alrua-karlstad.karlstad.toke.dk> <87a93oilxl.fsf@lifelogs.com> 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 1416326332 27829 80.91.229.3 (18 Nov 2014 15:58:52 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 18 Nov 2014 15:58:52 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Nov 18 16:58:45 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 1XqlAz-0001Es-Br for ged-emacs-devel@m.gmane.org; Tue, 18 Nov 2014 16:58:45 +0100 Original-Received: from localhost ([::1]:53907 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XqlAy-0002js-W5 for ged-emacs-devel@m.gmane.org; Tue, 18 Nov 2014 10:58:45 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:36113) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XqlAr-0002jh-5k for emacs-devel@gnu.org; Tue, 18 Nov 2014 10:58:42 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XqlAl-0007LD-I0 for emacs-devel@gnu.org; Tue, 18 Nov 2014 10:58:37 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:44440) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XqlAl-0007L8-BD for emacs-devel@gnu.org; Tue, 18 Nov 2014 10:58:31 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1XqlAj-00019r-AH for emacs-devel@gnu.org; Tue, 18 Nov 2014 16:58:29 +0100 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 ; Tue, 18 Nov 2014 16:58:29 +0100 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 ; Tue, 18 Nov 2014 16:58:29 +0100 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Original-Lines: 49 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.130012 (Ma Gnus v0.12) Emacs/25.0.50 (gnu/linux) Cancel-Lock: sha1:DEz3yEqu67RPVuRVhbzhZ2a2ZRg= 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:177571 Archived-At: On Tue, 18 Nov 2014 16:29:30 +0100 Lars Magne Ingebrigtsen wrote: LMI> Ted Zlatanov writes: TH> incidentally, does Emacs check the cipher mode of the connection TH> itself (I'm assuming this warning pertains to the certificate TH> itself, not the connection encryption). >> >> No, after establishing the connection we don't check its properties. In >> many cases, depending on the priority string, it could be very different >> from what we expected IIUC, so this is neither simple nor very useful. LMI> Well, yes, that's exactly what we do. Open the connection, and then LMI> check the properties. >"? You're checking the certificate, but not the cipher mode or anything else that was negotiated. I think that's what Toke meant. >> Also, would you like to integrate your TOFU patch with the new nsm branch? LMI> The NSM does TOFU. No patch necessary. Cool. >> I'm testing and using the NSM. The number one thing it needs is a >> `tabulated-list-mode' interface to review all the entries. See also my >> note about the GPG key management functionality, which I think naturally >> fits in the NSM. LMI> Sure... but since there's almost nothing human-readable (or something a LMI> machine can transform into something human-readable), I'm not quite sure LMI> what it should display... The list of explicitly saved security exceptions. LMI> I mean, I can see a user wanting to say to Emacs "delete everything you LMI> know about me contacting news.gmane.org", but there's no real way to LMI> match that up to the entries in the file unless you also know the port LMI> number/service name used. True, but I really don't see the harm in saving those in cleartext. Like I said, I would use a .gpg file if I was worried about leaking that data. With the current approach I think you'll see two problems: 1) cruft will accumulate, since you don't know what's what 2) when servers change names or ports, you don't know what to remove HTH Ted