crypto.ecdsa: migrate ecdsa.PrivateKey.new() to use high level api
#23640
+174
−100
Conversation
This file contains 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
|
Connected to Huly®: V_0.6-22063 |
blackshirt
changed the title
PrivateKey.new() to use high level apiecdsa.PrivateKey.new() to use high level api
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.
This PR was a continuation of migration step of this phase. In this PR, its only migrates one generator function
ecdsa.PrivateKey.new()to use high level api. Its also still use old deprecated api to support old function that relies onEC_KEYfunction.So, its does not changes the current behaviour, and the old opaque still avaialbles on there.
The other changes are:
Its is..
Happy days..