From: Lars Ingebrigtsen <larsi@gnus.org>
To: wilde@sha-bang.de
Cc: 48103@debbugs.gnu.org
Subject: bug#48103: 28.0.50; tls connection failing on invoking package-list-packages (and other operations)
Date: Wed, 05 May 2021 11:20:27 +0200 [thread overview]
Message-ID: <87mtt97d0k.fsf@gnus.org> (raw)
In-Reply-To: <874kfiljya.fsf@tammy.lan.sha-bang.de> (wilde@sha-bang.de's message of "Tue, 04 May 2021 15:14:37 +0200")
wilde@sha-bang.de writes:
>> Perhaps the version of gnutls on NetBSD doesn't support TLS 1.3?
>
> On my NetBSD system:
>
> % gnutls-cli -l | grep -i tls1.3
> TLS_AES_128_GCM_SHA256 0x13, 0x01 TLS1.3
> TLS_AES_256_GCM_SHA384 0x13, 0x02 TLS1.3
> TLS_CHACHA20_POLY1305_SHA256 0x13, 0x03 TLS1.3
> TLS_AES_128_CCM_SHA256 0x13, 0x04 TLS1.3
> TLS_AES_128_CCM_8_SHA256 0x13, 0x05 TLS1.3
> Protocols: VERS-TLS1.0, VERS-TLS1.1, VERS-TLS1.2, VERS-TLS1.3, VERS-DTLS0.9,
> VERS-DTLS1.0, VERS-DTLS1.2
>
> This output is identical to the output I get on my GNU/Linux system
> where the system does not exist. So I'd assume the TLS 1.3 support does
> not differ...
Doesn't sound like it, no, so I'm guessing there's something
timing-related and a problem with retries. Unfortunately, I'm not able
to build Emacs at all under Netbsd 9.0 (which is the version I have
here), so I'll have to install a new VM with 9.1 to do some testing.
That might take a while, though, so if somebody else can poke at this,
that'd be nice. :-)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-05-05 9:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 14:45 bug#48103: 28.0.50; tls connection failing on invoking package-list-packages (and other operations) wilde
2021-05-02 7:49 ` Lars Ingebrigtsen
2021-05-03 10:13 ` wilde
2021-05-04 9:01 ` Lars Ingebrigtsen
2021-05-04 13:14 ` wilde
2021-05-05 9:20 ` Lars Ingebrigtsen [this message]
2021-05-05 12:55 ` Robert Pluim
2021-05-06 9:13 ` Lars Ingebrigtsen
2021-05-06 12:59 ` Robert Pluim
2021-05-05 14:24 ` wilde
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=87mtt97d0k.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=48103@debbugs.gnu.org \
--cc=wilde@sha-bang.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).