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 12:40:33 -0500 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <87y4r8flv2.fsf@lifelogs.com> References: <85a93pj1n5.fsf@stephe-leake.org> <87sihg7r73.fsf@alrua-karlstad.karlstad.toke.dk> <87a93oilxl.fsf@lifelogs.com> <87oas4h555.fsf@lifelogs.com> <87a93oh180.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 1416332471 7982 80.91.229.3 (18 Nov 2014 17:41:11 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 18 Nov 2014 17:41:11 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Nov 18 18:41:04 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 1Xqmlz-0006Lr-JY for ged-emacs-devel@m.gmane.org; Tue, 18 Nov 2014 18:41:03 +0100 Original-Received: from localhost ([::1]:54538 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xqmlz-0000TA-6v for ged-emacs-devel@m.gmane.org; Tue, 18 Nov 2014 12:41:03 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40185) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XqmlN-0000Ik-OD for emacs-devel@gnu.org; Tue, 18 Nov 2014 12:40:31 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XqmlH-0003zw-Ud for emacs-devel@gnu.org; Tue, 18 Nov 2014 12:40:25 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:56281) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XqmlH-0003zr-OB for emacs-devel@gnu.org; Tue, 18 Nov 2014 12:40:19 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1XqmlD-00062P-Tq for emacs-devel@gnu.org; Tue, 18 Nov 2014 18:40:15 +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 18:40:15 +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 18:40:15 +0100 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Original-Lines: 43 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:k6qkKpgQFwHZ8SjE3IG2mfHi+68= 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:177606 Archived-At: On Tue, 18 Nov 2014 18:28:26 +0100 Lars Magne Ingebrigtsen wrote: LMI> Ted Zlatanov writes: LMI> 1) Drop certificate checking for images in shr. I mean, do we care? >> >> I think we care. LMI> What are the security implications of inserting an image from a source LMI> we can't validate? Malicious binary payloads in images are quite common. There are also attacks/exploits/hacks that load Javascript from images. Regardless, you'd be lowering the security level of the data exchange. LMI> 99% of the images aren't over TLS, anyway, and aren't validated... OK, but that's not relevant to the above :) LMI> 2) If being run from the async context (how do we check for that?), LMI> refuse to handle insecure TLS connections silently. >> >> Works for me, as long as the errors are reviewable in the NSM. I should >> be able to go somewhere and hit a button "allow this cert from now on". LMI> shr should really insert "broken image" markers into the buffers (and LMI> "loading images"), and then the user could just hit RET on one of the LMI> broken images and then get queried about the certificate LMI> interactively... OK with me, that's a good solution for this particular case. But there will be others where you can't see the things that went wrong in the background. I suggested a modeline indicator previously... it's better than silent failure, right? LMI> Which reminds me: We need a way to determine that Emacs is running LMI> non-interactively as well as being run from an async context. What's LMI> the way to do that? I know in non-interactive mode the minibuffer reads from stdio, so there's definitely some distinction for batch mode. But I don't know how to distinguish it in ELisp or check the async mode, sorry. Ted