From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.bugs Subject: bug#25061: consider adding %COMPAT to default gnutls priority string Date: Thu, 01 Dec 2016 13:32:43 -0500 Organization: =?UTF-8?Q?=D0=A2=D0=B5=D0=BE=D0=B4=D0=BE=D1=80_?= =?UTF-8?Q?=D0=97=D0=BB=D0=B0=D1=82=D0=B0=D0=BD=D0=BE=D0=B2?= @ Cienfuegos Message-ID: <878trzo5ys.fsf@lifelogs.com> References: <87zikiwpl6.fsf@igalia.com> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1480617200 7104 195.159.176.226 (1 Dec 2016 18:33:20 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 1 Dec 2016 18:33:20 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux) Cc: 25061@debbugs.gnu.org, ludo@gnu.org To: Andy Wingo Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Thu Dec 01 19:33:12 2016 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1cCWAR-0000NK-I2 for geb-bug-gnu-emacs@m.gmane.org; Thu, 01 Dec 2016 19:33:11 +0100 Original-Received: from localhost ([::1]:58166 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cCWAV-0003Sa-9Q for geb-bug-gnu-emacs@m.gmane.org; Thu, 01 Dec 2016 13:33:15 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:33973) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cCWAM-0003SS-K9 for bug-gnu-emacs@gnu.org; Thu, 01 Dec 2016 13:33:10 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cCWAJ-0008EF-98 for bug-gnu-emacs@gnu.org; Thu, 01 Dec 2016 13:33:06 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:33646) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cCWAJ-0008E6-5t for bug-gnu-emacs@gnu.org; Thu, 01 Dec 2016 13:33:03 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1cCWAI-0007Ic-Fy for bug-gnu-emacs@gnu.org; Thu, 01 Dec 2016 13:33:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Ted Zlatanov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 01 Dec 2016 18:33:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 25061 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 25061-submit@debbugs.gnu.org id=B25061.148061717428045 (code B ref 25061); Thu, 01 Dec 2016 18:33:02 +0000 Original-Received: (at 25061) by debbugs.gnu.org; 1 Dec 2016 18:32:54 +0000 Original-Received: from localhost ([127.0.0.1]:49045 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cCWA9-0007IH-PB for submit@debbugs.gnu.org; Thu, 01 Dec 2016 13:32:53 -0500 Original-Received: from mail-pg0-f42.google.com ([74.125.83.42]:35280) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cCWA7-0007I3-AL for 25061@debbugs.gnu.org; Thu, 01 Dec 2016 13:32:52 -0500 Original-Received: by mail-pg0-f42.google.com with SMTP id p66so97664382pga.2 for <25061@debbugs.gnu.org>; Thu, 01 Dec 2016 10:32:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lifelogs.com; s=google; h=from:to:cc:subject:organization:references:mail-copies-to :gmane-reply-to-list:date:in-reply-to:message-id:user-agent :mime-version; bh=kSX835QhAw4otLLMfVXUfMq2KBqGXFCg3VAIfmtZPC0=; b=AmefHVxSEzzqsjpa3km/K1fm4eqR5LIA4OdQ7b7rqa/H6ATpxOE7VLNsFB8TiAXEBn Le20BMzM4RlB3javiUB8UB/dyv9VTob/pKA8O7UWdGxqaN04TUxKwyjAvibhfa5NRTRO ww7z8SI8GYoGKfOBy9/w1bCPAnKV4AnH8DHpU= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:organization:references :mail-copies-to:gmane-reply-to-list:date:in-reply-to:message-id :user-agent:mime-version; bh=kSX835QhAw4otLLMfVXUfMq2KBqGXFCg3VAIfmtZPC0=; b=QgCkb11S/Wp12CyDOWoQ8CzntrmDkNyE46lIHqnmDWZa9cqL0l7FAvKNFCaBzvmrlF iNuoojQtPOxGVYb3HtrgZQk07xn9s2TTuNpzsQy4Pk5BCMRmyYXpVKiD/wyj26SMCRFA MT4SXoRORgyQHd16ppKvtrHtmjpB7ThLK8B40NhYs+w8od7gQX9PAWK9nGnpbfeFm+p9 F7ARBr1I4bSPaR/WjqQmKeOK+QGRUt256Lra++Tj4EjOTrJGp2AheSTMpbP7iXGORcOm 9GpMfYKY9JUuQMBLveOdH0bvZaXs66Du4rrXnr6Ov3SXYkbWmrskN4d9MXoxlYBSykxY GNIQ== X-Gm-Message-State: AKaTC02YcSlChE2YUYnJWd6GrlNbz8VmmiZQDW1TImDuhnUMrDL3dVm41fzG3ayQjibauA== X-Received: by 10.99.245.21 with SMTP id w21mr72657456pgh.5.1480617165599; Thu, 01 Dec 2016 10:32:45 -0800 (PST) Original-Received: from flea (c-98-229-60-157.hsd1.ma.comcast.net. [98.229.60.157]) by smtp.gmail.com with ESMTPSA id m66sm1927197pfm.3.2016.12.01.10.32.44 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 01 Dec 2016 10:32:45 -0800 (PST) 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 Gmane-Reply-To-List: yes In-Reply-To: <87zikiwpl6.fsf@igalia.com> (Andy Wingo's message of "Tue, 29 Nov 2016 11:24:53 +0100") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:126360 Archived-At: On Tue, 29 Nov 2016 11:24:53 +0100 Andy Wingo wrote: AW> There have been reports of errors from people using melpa and so on AW> which manifest themselves as: AW> gnutls.c: [0] (Emacs) fatal error: The TLS connection was non-properly terminated. ... AW> So, as Ludovic suggests in his message, a workaround might be: AW> (setq gnutls-algorithm-priority "NORMAL:%COMPAT") AW> See Ludovic's message for some justification. Just an idea. I have AW> been trying to reproduce the problem that people report locally as some AW> TLS errors but I have not been able to. We could break down %COMPAT to all its components and find which ones are causing the issue. I wouldn't make %COMPAT part of the default. For the sake of accessing some sites, we'd make all our users less secure. But if the connection fails, maybe we can suggest setting it for just that site. That's not trivial right now but I plan to add that capability. Ted