From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.devel Subject: Re: A couple of questions and concerns about Emacs network security Date: Sun, 24 Jun 2018 18:57:38 +0200 Message-ID: References: <83po0iuhs7.fsf@gnu.org> <83lgb4tg92.fsf@gnu.org> <838t74td5t.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1529859351 22040 195.159.176.226 (24 Jun 2018 16:55:51 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 24 Jun 2018 16:55:51 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: eggert@cs.ucla.edu, emacs-devel@gnu.org, Noam Postavsky , wyuenho@gmail.com To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jun 24 18:55:47 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fX8Ik-0005eW-Q0 for ged-emacs-devel@m.gmane.org; Sun, 24 Jun 2018 18:55:46 +0200 Original-Received: from localhost ([::1]:42545 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fX8Ks-0007UU-1q for ged-emacs-devel@m.gmane.org; Sun, 24 Jun 2018 12:57:58 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:36955) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fX8Ki-0007SG-Mt for emacs-devel@gnu.org; Sun, 24 Jun 2018 12:57:49 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fX8Kf-0004xX-K5 for emacs-devel@gnu.org; Sun, 24 Jun 2018 12:57:48 -0400 Original-Received: from hermes.netfonds.no ([80.91.224.195]:49184) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fX8Kf-0004vA-Cm; Sun, 24 Jun 2018 12:57:45 -0400 Original-Received: from cm-84.212.221.165.getinternet.no ([84.212.221.165] helo=stories) by hermes.netfonds.no with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1fX8KY-0004OF-VY; Sun, 24 Jun 2018 18:57:41 +0200 Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAGFBMVEUHBQYsHR0UDg8JCAcI BgaNfnAEAgMNCgpOWFu1AAACP0lEQVQ4jXWTTYvbMBCGB9b4LrXCZ4lsfU2Qqa4qGrJnLZheDV18 3tih+vt9R3aSbtnOwdjz6J0vj+gYnPrENC1ut1KWvshXX2BXUnp3f7R3svAu/7rXcKTtdNf5UC7d GkIF3h+RAzGD+umUPX1xp0U7H1bvr4SMOKBeUclJm4vSipP3fqAqrBYGzxz4QLwDcaagnFYXVBIj cUoAQUDywVptrdKWqa0SgD0U+8jMkamZkGV95GBkYCZq5yeRAKx7cj8IiO08EXGpodCK3WZnVd+7 cr4BzEuZrIWMGp38nndgtbMmb4oNTAP5gL5hFYw5awi/z40nyarMOBq4x1FpRH0ACxfYmE12APo8 TzswJgNohZHoXjmAdFfgvNLmFQV2AOQpDWkHcJo8vroe4E3AcFcoKwEFIAf7myIbqW4DbwI42a3U Mcsz98t5lkEOSF6PqlGwNv3SzjPmmDw7U2MpCamfu3KeZMDsB2e0+JWR3LZbYhNbaiBZFDTowELi MNFICNXgb1WADpx7HjERV3+WAHh24HKx1iH5LGBwD6urDjDVHHfvvvYVsCS/kcXpgkvyARS4oegg WI6EPqjusK9LJevTRPjo1zte/gaDII6CGxlWXWvmlyse8kL457yFGn7UC6IOVRzTShKgrqcsKAYq gtj4UqdYgd9zJCw8h3JTyEZbJx9nzC9tAEmwjilZd+XErYBSCHfkmvy9YtSKkeNuSzepqT28qP4r ycXBPFAVzVM7C6Ynd/g27zbVA5/Z/8EfB4kE0K3PlncAAAAASUVORK5CYII= In-Reply-To: <838t74td5t.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 24 Jun 2018 18:30:38 +0300") X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 80.91.224.195 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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" Xref: news.gmane.org gmane.emacs.devel:226663 Archived-At: Eli Zaretskii writes: > When the changes are pushed to master, we could look at them and > consider whether they (or some of their parts) are safe enough for > emacs-26. Yup. I'm going through the current recommendations for TLS security, and most of them are straightforward and require just some added NSM checks. However, the check for intermediary sha1 certificates checks requires a C-level change: gnutls.c doesn't expose to Lisp the certificate chain, so I'll have to add that, too. It's not a complicated addition, but it's C level, so you'll have to decide whether something that has the potential for crashing Emacs is worth the risk for Emacs 26.2. But I guess we'll see once I've implemented this (hopefully next week). -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no