Repository navigation
bpo-38820: OpenSSL 3.0.0: Use supported hashing algos in doc test (GH-25319) - #25319
Merged
tiran merged 1 commit intoApr 9, 2021
Merged
tiran merged 1 commit into
tiran merged 1 commit into
Conversation
Copy link
Copy Markdown
Member
Sorry, something went wrong.
ripemd160 is not available in OpenSSL 3.0.0's default crypto provider. It's only present in legacy provider. Signed-off-by: Christian Heimes <christian@python.org>
Copy link
Copy Markdown
Contributor
|
Thanks @tiran for the PR 🌮🎉.. I'm working now to backport this PR to: 3.8, 3.9. |
Sorry, something went wrong.
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this pull request
Apr 9, 2021
…thonGH-25319) ripemd160 is not available in OpenSSL 3.0.0's default crypto provider. It's only present in legacy provider. Signed-off-by: Christian Heimes <christian@python.org> (cherry picked from commit 2d7fdc9) Co-authored-by: Christian Heimes <christian@python.org>
Copy link
Copy Markdown
|
GH-25320 is a backport of this pull request to the 3.9 branch. |
Sorry, something went wrong.
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this pull request
Apr 9, 2021
…thonGH-25319) ripemd160 is not available in OpenSSL 3.0.0's default crypto provider. It's only present in legacy provider. Signed-off-by: Christian Heimes <christian@python.org> (cherry picked from commit 2d7fdc9) Co-authored-by: Christian Heimes <christian@python.org>
Copy link
Copy Markdown
|
GH-25321 is a backport of this pull request to the 3.8 branch. |
Sorry, something went wrong.
stratakis
pushed a commit
to stratakis/cpython
that referenced
this pull request
Mar 11, 2024
…thonGH-25319) ripemd160 is not available in OpenSSL 3.0.0's default crypto provider. It's only present in legacy provider. Signed-off-by: Christian Heimes <christian@python.org> (cherry picked from commit 2d7fdc9) Co-authored-by: Christian Heimes <christian@python.org>
mcepl
pushed a commit
to openSUSE-Python/cpython
that referenced
this pull request
Apr 2, 2024
…thonGH-25319) ripemd160 is not available in OpenSSL 3.0.0's default crypto provider. It's only present in legacy provider. Signed-off-by: Christian Heimes <christian@python.org> (cherry picked from commit 2d7fdc9) Co-authored-by: Christian Heimes <christian@python.org>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ripemd160 is not available in OpenSSL 3.0.0's default crypto provider.
It's only present in legacy provider.
Signed-off-by: Christian Heimes christian@python.org
https://bugs.python.org/issue38820