Skip to content

Conversation

@gpshead
Copy link
Member

@gpsheadgpshead commented May 11, 2019

Modern Linux distros such as Debian Buster have default OpenSSL system
configurations that reject connections to servers with weak certificates
and the use of TLS versions less than TLSv1.2 by default. This causes our
test suite run with external networking resources enabled to skip these tests
when they encounter such a failure or configuration.

(cherry picked from commit 2cc0223)

Additional change to test_ssl.py required as 3.6 and earlier have legacy protocol tests.
The test_httplib.py change is omitted from this backport as self-signed.pythontest.net's
certificate was updated.

Authored-by: Gregory P. Smith greg@krypto.org

https://bugs.python.org/issue35925

gpshead added 2 commits May 11, 2019 11:36
…pythonGH-13124) Modern Linux distros such as Debian Buster have default OpenSSL system configurations that reject connections to servers with weak certificates by default. This causes our test suite run with external networking resources enabled to skip these tests when they encounter such a failure. Fixing the network servers is a separate issue.. (cherry picked from commit 2cc0223) Co-authored-by: Gregory P. Smith <greg@krypto.org>
self-signed.pythontest.net was updated so the test_httplib change is no longer necessary.
@gpshead
Copy link
MemberAuthor

This will make the debian buster buildbot green again for 3.6.

@larryhastings you might want to cherry pick this for 3.5 as well if people building 3.5.x on systems with a modern openssl configuration and running -u all tests is a concern.

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

testsTests in the Lib/test dir

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@gpshead@ned-deily@the-knights-who-say-ni@bedevere-bot