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.
Observation
The
BigInteger#toByteArray()
method returns the minimum number of bytes required to represent the BigInteger, which means thatSpecific Case
Focusing in the
SharedSecretCalculation
and specifically the methodsrecomputeEcdsa256YFromX
andrecomputeEcdsa384YFromX
:The input byte array
publicKeyX
should have 32 (resp. 48) byte length.In the case that has a prefix of
0x00
bytes, the following would hold:Now, because the right version of the above byte array was consequently used, the input would have an incorrect length, which is why the process would fail to find an available Y COSE key.
Partial Solution
One simple solution is to pad left the converted array in order to make it have the correct length.
At least, this solves the problematic cases of zero-prefix inputs.