Skip to content

Conversation

@miss-islington
Copy link
Contributor

@miss-islington miss-islington commented Aug 30, 2018

Update all test certs and keys to use future proof crypto settings:

  • 3072 bit RSA keys
  • SHA-256 signature

Signed-off-by: Christian Heimes [email protected]
(cherry picked from commit e6dac00)

Co-authored-by: Christian Heimes [email protected]

https://bugs.python.org/issue34542

Update all test certs and keys to use future proof crypto settings:

* 3072 bit RSA keys
* SHA-256 signature

Signed-off-by: Christian Heimes <[email protected]>
(cherry picked from commit e6dac00)

Co-authored-by: Christian Heimes <[email protected]>
@miss-islington
Copy link
Contributor Author

@tiran: Backport status check is done, and it's a success ✅ .

1 similar comment
@miss-islington
Copy link
Contributor Author

@tiran: Backport status check is done, and it's a success ✅ .

@vstinner
Copy link
Member

vstinner commented Sep 4, 2018

@tiran: should we merge this backport to 3.7?

@stratakis
Copy link
Contributor

@vstinner This will be required by all the python versions compiled against openssl 1.1.1 with stricter default policy.

Although it doesn't totally fix the compatibility, some tests still fail, it addresses numerous issues.

@tiran
Copy link
Member

tiran commented Sep 6, 2018

@vstinner this is the backport to 3.7

For 3.6 and 2.7, I need to manually backport the fixes.

@tiran tiran merged commit 2d3f2dc into python:3.7 Sep 6, 2018
@miss-islington miss-islington deleted the backport-e6dac00-3.7 branch September 6, 2018 13:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants