From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Network security manager Date: Tue, 18 Nov 2014 19:43:40 +0200 Message-ID: <83h9xw9zg3.fsf@gnu.org> 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: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1416332652 11328 80.91.229.3 (18 Nov 2014 17:44:12 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 18 Nov 2014 17:44:12 +0000 (UTC) Cc: emacs-devel@gnu.org To: Lars Magne Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Nov 18 18:44:05 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 1Xqmov-0007hg-34 for ged-emacs-devel@m.gmane.org; Tue, 18 Nov 2014 18:44:05 +0100 Original-Received: from localhost ([::1]:54549 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xqmou-00036N-KY for ged-emacs-devel@m.gmane.org; Tue, 18 Nov 2014 12:44:04 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:41386) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xqmol-00035w-4O for emacs-devel@gnu.org; Tue, 18 Nov 2014 12:44:01 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xqmoe-0005Hw-5X for emacs-devel@gnu.org; Tue, 18 Nov 2014 12:43:55 -0500 Original-Received: from mtaout22.012.net.il ([80.179.55.172]:62493) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xqmod-0005Ha-UK for emacs-devel@gnu.org; Tue, 18 Nov 2014 12:43:48 -0500 Original-Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0NF800500X67O900@a-mtaout22.012.net.il> for emacs-devel@gnu.org; Tue, 18 Nov 2014 19:43:46 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NF8005ULX8X4F90@a-mtaout22.012.net.il>; Tue, 18 Nov 2014 19:43:46 +0200 (IST) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 X-Received-From: 80.179.55.172 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:177609 Archived-At: > From: Lars Magne Ingebrigtsen > Date: Tue, 18 Nov 2014 18:28:26 +0100 > > shr should really insert "broken image" markers into the buffers (and > "loading images"), and then the user could just hit RET on one of the > broken images and then get queried about the certificate > interactively... Do that, and you've added one more reason for me to disable the whole darn thing right away. I mean, how much annoyance should one endure to be "secure"? is there any limit? > Which reminds me: We need a way to determine that Emacs is running > non-interactively as well as being run from an async context. What's > the way to do that? It's in the manual, I'd say.