From: ludo@gnu.org (Ludovic Courtès)
To: 23311-done@debbugs.gnu.org
Subject: bug#23311: TLS handshake error
Date: Wed, 20 Apr 2016 13:18:38 +0200 [thread overview]
Message-ID: <877ffsy1dd.fsf@gnu.org> (raw)
In-Reply-To: <87y48a7dpd.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 19 Apr 2016 00:29:50 +0200")
ludo@gnu.org (Ludovic Courtès) skribis:
> $ while ./pre-inst-env guix download https://mirror.hydra.gnu.org/index.html ; do : ; done
Interestingly, the same loop with wget (which uses the very same GnuTLS)
goes on forever.
It turns out that instead of the default TLS cipher suite priority
string (“NORMAL”), wget does:
--8<---------------cut here---------------start------------->8---
case secure_protocol_auto:
err = gnutls_priority_set_direct (session, "NORMAL:%COMPAT:-VERS-SSL3.0", NULL);
break;
--8<---------------cut here---------------end--------------->8---
The code doesn’t explain why, but GnuTLS’s documentation has this bit
(info "(gnutls) Priority Strings"):
--8<---------------cut here---------------start------------->8---
%COMPAT will enable compatibility
mode. It might mean that
violations of the protocols
are allowed as long as maximum
compatibility with problematic
clients and servers is
achieved. More specifically
this string would disable TLS
record random padding,
tolerate packets over the
maximum allowed TLS record,
and add a padding to TLS
Client Hello packet to prevent
it being in the 256-512 range
which is known to be causing
issues with a commonly used
firewall.
--8<---------------cut here---------------end--------------->8---
Indeed, as soon as we add %COMPAT, ‘gnutls-cli’ et al. send a 253-byte
client hello (instead of 261) and the problem vanishes.
Commit 967ee481e893fd77ff8ca896188e20e425331bf2 does that.
Ludo’.
next prev parent reply other threads:[~2016-04-20 11:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 22:29 bug#23311: TLS handshake error Ludovic Courtès
2016-04-19 14:06 ` Ludovic Courtès
2016-04-19 21:10 ` Ludovic Courtès
2016-04-19 21:51 ` Ludovic Courtès
2016-04-20 11:18 ` Ludovic Courtès [this message]
2016-04-20 11:31 ` Mathieu Lirzin
2016-04-20 15:32 ` Ludovic Courtès
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877ffsy1dd.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=23311-done@debbugs.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 public inbox
https://git.savannah.gnu.org/cgit/guix.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).