From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Juanma Barranquero Newsgroups: gmane.emacs.devel Subject: Re: GnuTLS for W32 Date: Fri, 6 Jan 2012 01:59:32 +0100 Message-ID: References: <87fwfvsgfv.fsf@wanadoo.es> <877h17scdo.fsf@wanadoo.es> <87hb0b77nr.fsf@lifelogs.com> <8739bvs27m.fsf@wanadoo.es> <87ty4b4329.fsf@lifelogs.com> <87hb0b3yoe.fsf@lifelogs.com> <6ED011D5-E185-44C6-BB31-A445A4E5F83A@gmail.com> <87wr976otx.fsf@lifelogs.com> <87ipkq6yy5.fsf@lifelogs.com> <87boqi6tzz.fsf@linux-hvfx.site> <87ehve3ul8.fsf@lifelogs.com> <87lipl22xm.fsf@lifelogs.com> <87boqh20ha.fsf@lifelogs.com> <877h151x01.fsf@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1325811624 2677 80.91.229.12 (6 Jan 2012 01:00:24 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 6 Jan 2012 01:00:24 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jan 06 02:00:20 2012 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1RiyAO-0004pk-3A for ged-emacs-devel@m.gmane.org; Fri, 06 Jan 2012 02:00:20 +0100 Original-Received: from localhost ([::1]:52460 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RiyAN-0007J3-Lk for ged-emacs-devel@m.gmane.org; Thu, 05 Jan 2012 20:00:19 -0500 Original-Received: from eggs.gnu.org ([140.186.70.92]:55353) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RiyAK-0007In-2R for emacs-devel@gnu.org; Thu, 05 Jan 2012 20:00:16 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RiyAI-0008Rv-T9 for emacs-devel@gnu.org; Thu, 05 Jan 2012 20:00:16 -0500 Original-Received: from mail-pw0-f41.google.com ([209.85.160.41]:48403) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RiyAI-0008RK-Lx for emacs-devel@gnu.org; Thu, 05 Jan 2012 20:00:14 -0500 Original-Received: by pbdd2 with SMTP id d2so1025140pbd.0 for ; Thu, 05 Jan 2012 17:00:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; bh=wwaLZ0Lt7wzmWbAAuHZ5noDh41CeS2+d0m5RC4NbMKE=; b=E5157rPlzgCPVkBSuWV1SXIxIKgGq5QAzS/V+I+GQck3YwTqRgDd+XUs3xKhpNB7M0 QH9aK/fXqYcWE+aiFVc0W1eN1xoCxMQzKI93eSgbM5O870SCPIGul413Q76/FPPQLu7o QLRCT3a5ktwZxKGbVK7rjt1rDyMOXayV8mXLw= Original-Received: by 10.68.199.231 with SMTP id jn7mr10189023pbc.125.1325811613476; Thu, 05 Jan 2012 17:00:13 -0800 (PST) Original-Received: by 10.142.247.28 with HTTP; Thu, 5 Jan 2012 16:59:32 -0800 (PST) In-Reply-To: <877h151x01.fsf@lifelogs.com> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-Received-From: 209.85.160.41 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:147376 Archived-At: 2012/1/6 Ted Zlatanov : > No, what I was proposing was a startup check that the "gnutls-critical" > package is up to date, meaning what the user has installed is the > latest on the GNU ELPA. At the end of the "gnutls-critical" chain, the intention is, either to update non-binaries (gnutls.c, gnutls.el), or binaries (the DLL). In the first case, I don't know why do we need such a special mechanism (security releases have been handled before, just by issuing a new release or an updated tarball); in the second case, you already know my objections, so I won't repeat them again. > The "gnutls-critical" package may do more afterwards, depending on the > OS. =C2=A0On W32 it may trigger a patch eventually. =C2=A0At first it wil= l just > display a warning, as Chad suggested. And then, we're going to implement something similar for image libraries, because they can also have security-related bugs. Aren't we? We could also make our own MinGW/MSYS distribution, for people that builds their own Windows Emacs. We would automatically upgrade it in case there's a security issue. And let's not forget binutils, and texinfo. Yes, I'm being facetious. Or not, I'm not sure anymore. > I think the C glue to GnuTLS is an Emacs component, deeply embedded. > The point of an exploit is that it can cross the barrier between "not a > component/not our problem" and "oh crap." Lots of code in Emacs calls external tools (from grep to nslookup to make). Anyone of them could turn into an "oh crap" moment. But we don't feel the impulse to distribute grep and make sure it is up to date. > I believe `open-network-stream' can use GnuTLS for HTTPS connections, > which matters for a lot of cases, e.g. package.el. I disagree with "a lot of cases". There are a few Emacs components that connect to the network, but it is perfectly possible (and, I think, even common) not to need them on Windows. >=C2=A0I agree about the image libraries, though, they should also be inclu= ded in an installer. As long as you say "an installer" and do not say "automatically check", I'm fine. > I need the "gnutls-critical" startup check or some other way to tell the > user their GnuTLS version is at risk *by default*. s/need/want/. =C2=A0 =C2=A0 Juanma