emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#25061: closed (consider adding %COMPAT to default


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#25061: closed (consider adding %COMPAT to default gnutls priority string)
Date: Fri, 15 Dec 2017 04:19:02 +0000

Your message dated Thu, 14 Dec 2017 23:18:21 -0500
with message-id <address@hidden>
and subject line Re: bug#25061: consider adding %COMPAT to default gnutls 
priority string
has caused the debbugs.gnu.org bug report #25061,
regarding consider adding %COMPAT to default gnutls priority string
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
25061: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=25061
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: consider adding %COMPAT to default gnutls priority string Date: Tue, 29 Nov 2016 11:24:53 +0100 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)
There have been reports of errors from people using melpa and so on
which manifest themselves as:

    gnutls.c: [0] (Emacs) fatal error: The TLS connection was non-properly 
terminated.

However I think maybe that's just the symptom and not the cause; see the
previous report:

    https://debbugs.gnu.org/cgi/bugreport.cgi?bug=25060

Ludovic Court├Ęs was seeing a similar issue to the one that people are
reporting for melpa etc in Guix, where we also use GnuTLS though not in
Emacs.  He then found that GNU wget, which also uses GnuTLS, wasn't
exhibiting the same behavior.  He was eventually able to reproduce the
problem with just gnutls-cli.  He tracked down the difference in that if
he adds %COMPAT to the priority list, then he has no problems:

    https://lists.gnu.org/archive/html/bug-guix/2016-04/msg00098.html
    http://bugs.gnu.org/23311

Note that the problem only exhibits itself for some web sites, and only
some of the time.  It manifested itself as a timeout where the server
would get stuck, which could explain that people are unable to fetch
packages then blame the problem on the spurious post-close error message
from bug 25060.

So, as Ludovic suggests in his message, a workaround might be:

    (setq gnutls-algorithm-priority "NORMAL:%COMPAT")

See Ludovic's message for some justification.  Just an idea.  I have
been trying to reproduce the problem that people report locally as some
TLS errors but I have not been able to.

Andy



--- End Message ---
--- Begin Message --- Subject: Re: bug#25061: consider adding %COMPAT to default gnutls priority string Date: Thu, 14 Dec 2017 23:18:21 -0500 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux)
On Mon, 11 Dec 2017 17:40:05 +0200 Eli Zaretskii <address@hidden> wrote: 

>> Can anyone knowledgeable comment on any possible downsides to this? I'll
>> wait 3 days for objections, then make the change in emacs-26.

EZ> Sounds like a good plan, thanks.

OK; done.

Ted


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]