From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: matei.alexandru@live.com, 45821@debbugs.gnu.org
Subject: bug#45821: Emacs UDP support on Windows
Date: Mon, 02 Jan 2023 14:41:00 +0200 [thread overview]
Message-ID: <83wn651543.fsf@gnu.org> (raw)
In-Reply-To: <877cy5kzhw.fsf@gmail.com> (message from Robert Pluim on Mon, 02 Jan 2023 11:22:03 +0100)
> Cc: "45821@debbugs.gnu.org" <45821@debbugs.gnu.org>
> From: Robert Pluim <rpluim@gmail.com>
> Date: Mon, 02 Jan 2023 11:22:03 +0100
>
> Alex> ❌ Indeed, TLS is broken -> Eww to https://www.gnu.org<https://www.gnu.org/> fails to load the page ( see attached image – Emacs instance on the left, compiled with UDP patch, didn’t load gnu.org while on the right side- default Emacs build for 28.1 opens it without any issues)
>
> Yep. Last time I looked at this, the TLS handshaking fails to complete
> (see src/process.c around line 5329 and the checking against
> GNUTLS_EMACS_HANDSHAKES_LIMIT) which means weʼre continually retrying
> the handshake without giving the remote end a chance to send us
> anything. Which I think means that our state machine for TLS
> negotiation is subtly incorrect, but only on MS-Windows.
On MS-Windows, there's another state machine involved, the one
vis-a-vis the reader thread we start to read the stuff from the
network connection. See reader_thread and sys_select in w32proc.c and
sys_write, sys_read, _sys_read_ahead, _sys_wait_accept, and
_sys_wait_connect in w32.c.
next prev parent reply other threads:[~2023-01-02 12:41 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 18:08 bug#45821: 28.0.50; Add UDP support for Emacs on Windows Lars Ingebrigtsen
2021-01-12 18:38 ` Eli Zaretskii
2021-01-13 9:17 ` Robert Pluim
2021-07-20 15:41 ` Lars Ingebrigtsen
2021-09-27 16:47 ` Robert Pluim
2021-09-27 17:45 ` Robert Pluim
2021-10-04 17:47 ` Robert Pluim
2021-10-04 17:59 ` Eli Zaretskii
2021-09-27 18:45 ` Eli Zaretskii
2021-10-11 11:56 ` Stefan Kangas
2021-10-11 12:06 ` Robert Pluim
2022-05-03 18:56 ` bug#45821: Emacs UDP support " Alex Matei
2022-05-04 7:35 ` Robert Pluim
2022-05-04 11:50 ` Alex Matei
2022-05-04 12:32 ` Robert Pluim
2022-09-11 11:26 ` bug#45821: 28.0.50; Add UDP support for Emacs " Lars Ingebrigtsen
2023-01-01 23:01 ` bug#45821: Emacs UDP support " Alex Matei
2023-01-02 0:47 ` Alex Matei
2023-01-02 10:22 ` Robert Pluim
2023-01-02 12:41 ` Eli Zaretskii [this message]
2023-01-02 13:29 ` Robert Pluim
2023-01-02 13:38 ` Eli Zaretskii
2023-01-02 22:56 ` Alex Matei
2023-01-03 8:51 ` Robert Pluim
2023-01-03 20:22 ` Alex Matei
2023-01-04 9:32 ` Robert Pluim
2023-01-04 10:15 ` Alex Matei
2023-01-04 10:50 ` Robert Pluim
2023-01-05 19:06 ` Alex Matei
2023-01-05 20:53 ` Alex Matei
2023-01-05 21:01 ` Alex Matei
2023-01-06 7:56 ` Robert Pluim
2023-01-07 11:24 ` Robert Pluim
2023-01-08 15:31 ` Alex Matei
2023-01-08 15:42 ` Robert Pluim
2023-01-08 15:43 ` Alex Matei
2023-01-08 16:00 ` Alex Matei
2023-01-08 16:08 ` Eli Zaretskii
2023-01-08 16:10 ` Alex Matei
2023-01-10 12:41 ` Alex Matei
2023-01-10 13:56 ` Robert Pluim
2023-01-11 13:09 ` Alex Matei
2023-01-11 13:23 ` Alex Matei
2023-01-12 9:22 ` Robert Pluim
2023-01-12 10:08 ` Eli Zaretskii
2023-01-12 10:14 ` Alex Matei
2023-01-12 10:24 ` Robert Pluim
2023-01-12 10:46 ` Eli Zaretskii
2023-01-12 10:57 ` Alex Matei
2023-01-12 10:59 ` Alex Matei
2023-01-12 11:03 ` Eli Zaretskii
2023-01-12 11:12 ` Alex Matei
2023-01-12 11:21 ` Robert Pluim
2023-01-12 11:23 ` Alex Matei
2023-01-12 11:18 ` Robert Pluim
2023-01-12 12:25 ` Eli Zaretskii
2023-01-12 13:28 ` Robert Pluim
2023-01-28 21:17 ` Alex Matei
2023-01-29 6:13 ` Eli Zaretskii
2023-01-02 10:10 ` Robert Pluim
2023-01-02 16:01 ` Alex Matei
2023-01-03 13:30 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-03 19:18 ` Alex Matei
2023-01-02 12:07 ` Eli Zaretskii
2023-01-02 15:59 ` Alex Matei
2023-01-02 17:01 ` Eli Zaretskii
2023-01-02 17:57 ` Alex Matei
2023-01-02 19:07 ` Alex Matei
2023-01-02 19:22 ` Eli Zaretskii
2023-01-02 19:24 ` Alex Matei
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=83wn651543.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=45821@debbugs.gnu.org \
--cc=matei.alexandru@live.com \
--cc=rpluim@gmail.com \
/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).