wycheproof2blb: secp256k1 with P1363 format #1092
Merged
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
parsing ecdsa_secp256k1_sha256_p1363_test.json
|
I guess these are vectors for the IEEE P1363, which unless it also goes by some other name (which I can't verify because I don't have access to the document) we don't support. From Wikipedia:
From what I can tell this is some other form of message encoding beyond the existing ones we support. |
|
The legacy IEEE 1363 has a very simple signature format with only r + s, totaling 64 bytes. I’ve searched some P1363 signatures in the test cases, and they are unique, not just copied from other cases. |
|
Aah, never heard it referred to that way. It's what we call just |
tarcieri
approved these changes
Jul 27, 2024
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.
parsing ecdsa_secp256k1_sha256_p1363_test.json