]> granicus.if.org Git - python/commit
Issue #25940: Use self-signed.pythontest.net in SSL tests
authorMartin Panter <vadmium+py@gmail.com>
Thu, 14 Jan 2016 09:36:00 +0000 (09:36 +0000)
committerMartin Panter <vadmium+py@gmail.com>
Thu, 14 Jan 2016 09:36:00 +0000 (09:36 +0000)
commit3d81d93f34937a445dc86c80820d48ae52080256
tree6fc1e8ca50ba44cddf498b21d10cfc09b705bc21
parent89644d080b9663ab1a809113b965e4e33a9a7af1
Issue #25940: Use self-signed.pythontest.net in SSL tests

This is instead of svn.python.org, whose certificate recently expired, and
whose new certificate uses a different root certificate.

The certificate used at the pythontest server was modifed to set the "basic
constraints" CA flag. This flag seems to be required for test_get_ca_certs_
capath() to work (in Python 3.4+).

Added the new self-signed certificate to capath with the following commands:

cp Lib/test/{selfsigned_pythontestdotnet.pem,capath/}
c_rehash -v Lib/test/capath/
c_rehash -v -old Lib/test/capath/
# Note the generated file names
cp Lib/test/capath/{selfsigned_pythontestdotnet.pem,0e4015b9.0}
mv Lib/test/capath/{selfsigned_pythontestdotnet.pem,ce7b8643.0}

The new server responds with "No route to host" when connecting to port 444.
Lib/test/capath/0e4015b9.0 [new file with mode: 0644]
Lib/test/capath/ce7b8643.0 [new file with mode: 0644]
Lib/test/https_svn_python_org_root.pem [deleted file]
Lib/test/selfsigned_pythontestdotnet.pem
Lib/test/test_ssl.py
Misc/NEWS