bug#27658: 26.0.50; response parsing hangs when using tls.el and gnutls-cli.exe on Windows

[Robert Pluim <rpluim@gmail.com>]

Richard Copley <rcopley@gmail.com> writes:

> On 13 Jul 2017 16:49, "Eli Zaretskii" <eliz@gnu.org> wrote:
>> Are you sure that blog is still accurate?  It's quite old, and newer
>> versions of the GnuTLS library became meanwhile available.
>>
>
> No doubt some stuff there is no longer valid, but the test case should
> succeed.
>
> I have the latest release of GnuTLS and I did my own testing and
> debugging using gnutls-cli.exe before writing this bug report.
>
> I mentioned the library in my last message. I find (on my own system
> today) that the Emacs TLS implementation using the library (in
> gnutls.{c,el}) works except that it accepts bad certificates. I don't
> think that's stated in the blog at all -- the blog is also mostly
> about the implementation based on an external program (in tls.el).

I've not been able to locate this blog entry. Could you point me at
it? Or provide details of hosts providing bad certificates that emacs
accepts when it shouldn't? Perhaps the default settings of GnuTLS in
emacs need tweaking.

> The possible bug in gnutls.{c,el} or the library itself, the one I was
> talking about in my last message, appears to be what is spoken about
> here(1) in November 2015 and here(2) in February 2016. As far as I
> know it doesn't have an Emacs bug report.
>

(2) leads to an Emacs bug report that is marked fixed. (1) is unclear
to me, I'll have to keep reading.

> (1)
> https://emacs.stackexchange.com/questions/18079/emacs-tls-check-is-still-ill-configured
> (2) https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816063