From: Noam Postavsky <npostavs@gmail.com>
To: thomas@m3y3r.de
Cc: 32658@debbugs.gnu.org
Subject: bug#32658: gnutls + non-blocking url-retrieve
Date: Thu, 16 May 2019 09:14:56 -0400 [thread overview]
Message-ID: <87mujmee27.fsf@gmail.com> (raw)
In-Reply-To: <864ldx6fga.fsf@DESKTOP-DQBDJ0U.i-did-not-set--mail-host-address--so-tickle-me> (thomas@m3y3r.de's message of "Sun, 07 Oct 2018 15:42:29 +0200")
thomas@m3y3r.de writes:
>>>> From: thomas@m3y3r.de
>>>>
>>>> 1.) I needed to revert to gnutls 3.5.19, the mingw64 build from the
>>>> gitlab ci build seems to have a working gnutls-cli tools on windows 10.
>>>> the gitlab builds for 3.6.3 and 3.6.4 seems to have another bug
>>>> (error code -53) in the gnutls-cli command.
>>>>
>>>> so only gnutls 3.5.19 have a working gnutls-cli. i installed this version in emacs 26.1
> okay, some more infos.
>
> I was able to bootstrap the emacs compile with mingw64.
>
> while I was trying to debug this problem with fprintf, eww suddenly
> started to work!!
>
> It started to work after I did insert an fprintf after the
> gnutls_try_handshake call in process.c !!
>
> what is going on here?
It sounds like this might be Bug#34341, the problem was
emacs_gnutls_read didn't handle GNUTLS_E_AGAIN properly. The symptoms
only seem to occur with servers supporting TLS1.3 and more recent gnutls
versions (I thought it was 3.6+, but I haven't pinned the precise
version numbers, so maybe 3.5.19 has it too, or maybe it's a bit
different on Windows). And some people reported that increasing
gnutls-log-level made it go away, so it's certainly timing dependent.
So can you check if the problem is fixed in the latest emacs-26 or
master branch?
https://debbugs.gnu.org/34341
next prev parent reply other threads:[~2019-05-16 13:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-07 9:22 bug#32658: 26.1; Cannot connect to TLS websites thomas
2018-09-30 21:33 ` bug#32658: gnutls + non-blocking url-retrieve thomas
2018-10-01 6:03 ` Eli Zaretskii
2018-10-01 20:48 ` thomas
2018-10-05 18:25 ` Noam Postavsky
2018-10-03 14:15 ` thomas
2018-10-07 13:42 ` thomas
2019-05-16 13:14 ` Noam Postavsky [this message]
2019-09-24 5:18 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mujmee27.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=32658@debbugs.gnu.org \
--cc=thomas@m3y3r.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).