From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: eggert@cs.ucla.edu, emacs-devel@gnu.org
Subject: Re: master e87e6a2: Fix unlikely races with GnuTLS, datagrams
Date: Wed, 13 Feb 2019 17:09:05 +0100 [thread overview]
Message-ID: <m21s4b8yce.fsf@gmail.com> (raw)
In-Reply-To: <835ztnpvbq.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 13 Feb 2019 17:22:17 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Robert Pluim <rpluim@gmail.com>
>> Date: Wed, 13 Feb 2019 14:09:44 +0100
>> Cc: Paul Eggert <eggert@cs.ucla.edu>
>>
>> eggert@cs.ucla.edu (Paul Eggert) writes:
>>
>> > branch: master
>> > commit e87e6a24c49542111e669b7d0f1a412024663f8e
>> > Author: Paul Eggert <eggert@cs.ucla.edu>
>> > Commit: Paul Eggert <eggert@cs.ucla.edu>
>> >
>> > Fix unlikely races with GnuTLS, datagrams
>>
>> Paul,
>>
>> there have been reports on help-gnu-emacs of emacs-26.1 failing when
>> using TLS 1.3 to talk to Google servers, and Iʼve just noticed it here
>> as well (although only in unusual circumstances). emacs-27 doesnʼt
>> have this issue, and cherry-picking this commit to emacs-26 fixes it
>> for me. Perhaps we could apply it there?
>
> It's too invasive and was too recently committed to go to the release
> branch, sorry.
OK. We'll just have to live with it for the moment then (Iʼm not about
to propose to people that they switch off TLS1.3 support, since
they'll forget to turn it back on).
Amusingly I only see it because itʼs triggered by
network-security-level > medium, which must change some timing
somewhere (adding logging or running nsm non-byte-compiled makes it go
away).
Robert
prev parent reply other threads:[~2019-02-13 16:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190116075252.11329.86219@vcs0.savannah.gnu.org>
[not found] ` <20190116075253.D88B420536@vcs0.savannah.gnu.org>
2019-02-13 13:09 ` master e87e6a2: Fix unlikely races with GnuTLS, datagrams Robert Pluim
2019-02-13 15:22 ` Eli Zaretskii
2019-02-13 16:09 ` Robert Pluim [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m21s4b8yce.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.