fix: pad elliptic curve coordinates correctly in JWK representation #22
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.
When creating and using JWK representations the byte array is padded at the start with 0x00 to ensure that all hashes of the JWK will be correct.
When calculating the hashed token in
parse.go
and when creating proofs increate.go
theFillBytes(buf []byte)
function is used on the big.Int to get the byte array representation with added zeros at the start.Checklist before requesting a review