Re: Special configuration needed for eww + gnutls? [emacs 28.1]

[Robert Pluim]

>>>>> On Fri, 15 Apr 2022 12:53:51 -0400, Kaushal Modi <kaushal.modi@gmail.com> 
>>>>> said:

    Kaushal> On Thu, Apr 14, 2022 at 10:04 PM Jude DaShiell 
<jdashiel@panix.com> wrote:
    >> 
    >> have you got this in one of your initialization files:
    >> (setq gnutls-algorithm-priority "NORMAL:-VERS-TLS1.3")

    Kaushal> No, gnutls-algorithm-priority is nil at its default value.

    Kaushal> If I evaluate this in an emacs -Q session:

    Kaushal> (progn
    Kaushal>   (setq gnutls-algorithm-priority "NORMAL:-VERS-TLS1.3")
    Kaushal>   (eww "https://scripter.co";))

    Kaushal> I see the eww buffer pop up but then stay stuck at "Contacting 
host:
    Kaushal> scripter.co:443".

    Kaushal> And if I evaluate

    Kaushal> (progn
    Kaushal>   (setq gnutls-algorithm-priority "NORMAL:-VERS-TLS1.2")
    Kaushal>   (eww "https://scripter.co";))

    Kaushal> I see

    Kaushal> Contacting host: scripter.co:443
    Kaushal> #<buffer  *http scripter.co:443*-871644>
    Kaushal> gnutls.c: [0] (Emacs) Received alert:  Error in protocol version

    Kaushal> If this info is useful, pkg-config --modversion gnutls returns 
3.3.29.
    Kaushal> (and so C-h v libgnutls-version also returns 30329).

scripter.co works for me with GnuTLS 3.7.1

This might be the Letʼs Encrypt cross-signing certificate expiry
issue, which is fixed in GnuTLS >= 3.6.14 See eg
<https://blog.germancoding.com/2021/04/16/lets-encrypt-and-expired-root-certificates/>

(although Iʼm wondering why itʼs taken so long for you to notice)

Robert
--