_sslutil__be_less_strict_about_which_ciphers_are_allowed_when_using___insecure
authorDebian Python Team <team+python@tracker.debian.org>
Mon, 11 Apr 2022 12:08:09 +0000 (13:08 +0100)
committerJulien Cristau <jcristau@debian.org>
Mon, 11 Apr 2022 12:08:09 +0000 (13:08 +0100)
commitb630a03fa7b1263aebe2d4da6d94a06b3c57e689
tree7bb9bcc461e42040152eb4f05e442b4ff72c49d9
parentb62e493eebefc81060d21fb0fbf3f396a385b6bc
_sslutil__be_less_strict_about_which_ciphers_are_allowed_when_using___insecure

# HG changeset patch
# User Julien Cristau <jcristau@debian.org>
# Date 1649507032 -7200
#      Sat Apr 09 14:23:52 2022 +0200
# Node ID c871c4fbc94f88e8c78a6bd4ece15d239cbdea10
# Parent  410916fc5935c7855c2cf4876d8311d34aabc29a
sslutil: be less strict about which ciphers are allowed when using --insecure

Python 3.10 restricted which ciphers are enabled by default, leading to
no available ciphers for TLS < 1.2.  When using the --insecure flag we
allow old TLS, so also adjust the cipher list to give connections a
chance to work.

On the server side, also loosen the cipher selection in tests (when
using the devel.serverexactprotocol option).

Differential Revision: https://phab.mercurial-scm.org/D12489

Gbp-Pq: Topic py310
Gbp-Pq: Name 4_sslutil__be_less_strict_about_which_ciphers_are_allowed_when_using___insecure.patch
mercurial/sslutil.py