Remove get_random_bytes from cryptography backend#381
Merged
Conversation
The RAND_bytes binding has been removed in cryptography 45.0. The recommendation[1] is now to rely on `os.urandom`, which is already implemented in the native backend. The pycrpto implementation was removed earlier, so this removes the leftover attempt to import it. Closes: mpdavis#380 [1] https://cryptography.io/en/latest/random-numbers/
69375a2 to
752abd2
Compare
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.
The RAND_bytes binding has been removed in cryptography 45.0. The
recommendation[1] is now to rely on
os.urandom, which is alreadyimplemented in the native backend.
The pycrpto implementation was removed earlier, so this removes the
leftover attempt to import it.
Closes: #380
[1] https://cryptography.io/en/latest/random-numbers/