unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Daiki Ueno <ueno@gnu.org>
Cc: 49035@debbugs.gnu.org, Emmanuel Agullo <emmanuel.agullo@inria.fr>,
	gnutls-help@lists.gnutls.org
Subject: bug#49035: [gnutls-help] TLS downgrade at bitbucket.org
Date: Sun, 20 Jun 2021 23:26:13 +0200	[thread overview]
Message-ID: <87wnqo6xe2.fsf@gnu.org> (raw)
In-Reply-To: <87tultyjcl.fsf-ueno@gnu.org> (Daiki Ueno's message of "Sat, 19 Jun 2021 17:17:30 +0200")

Hi Daiki,

Daiki Ueno <ueno@gnu.org> skribis:

> Ludovic Courtès <ludo@gnu.org> writes:
>
>> $ gnutls-cli --priority="NORMAL:-ARCFOUR-128:-CTYPE-ALL:+CTYPE-X509:-VERS-SSL3.0:-VERS-TLS-ALL:+VERS-TLS1.0:+VERS-TLS1.1:+VERS-TLS1.2:+VERS-TLS1.3" -p https bitbucket.org

[...]

>> Aren’t these two priority strings supposed to be equivalent today?
>
> No.  If -VERS-TLS-ALL is used, the default priorities on TLS versions in
> NORMAL are ignored; the user is responsible for building the priority
> string so it reflects the actual preference, which in this case is:
>
>   -VERS-TLS-ALL:+VERS-TLS1.3:+VERS-TLS1.2:+VERS-TLS1.1:+VERS-TLS1.0

Thanks for the explanations.  As you suggest, the mistake was that cURL
7.77.0 would pass the priority string in the “wrong order”, preferring
older TLS versions.  This is now fixed:

  https://github.com/curl/curl/issues/7277

Ludo’.




      reply	other threads:[~2021-06-20 21:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-15  9:16 bug#49035: Git 2.32.0 fails with ‘gnutls_handshake’ error Ludovic Courtès
2021-06-15 12:38 ` Ludovic Courtès
2021-06-15 21:51   ` bug#49035: TLS downgrade at bitbucket.org Ludovic Courtès
2021-06-18 12:10     ` bug#49035: Git 2.32.0 fails with ‘gnutls_handshake’ error Ludovic Courtès
2021-06-18 15:43       ` Ludovic Courtès
2021-06-19 15:17     ` bug#49035: [gnutls-help] TLS downgrade at bitbucket.org Daiki Ueno
2021-06-20 21:26       ` Ludovic Courtès [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

  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=87wnqo6xe2.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=49035@debbugs.gnu.org \
    --cc=emmanuel.agullo@inria.fr \
    --cc=gnutls-help@lists.gnutls.org \
    --cc=ueno@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).