You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For Ed256 and HSS-LMS, the signature validation routine needs the public key, the buffer that contains the (supposedly) signed content, the signature value, and the signature algorithm identifier. I suggest that this be the API for all signature validation, and in the ES256 case, the SHA-256 have value can be computed inside the ES256_verify function.
The text was updated successfully, but these errors were encountered:
It looks like the only difference between the current API and the one you've suggested is whether COSEAuthVerify does the lookup of the public key. Is that right?
For Ed256 and HSS-LMS, the signature validation routine needs the public key, the buffer that contains the (supposedly) signed content, the signature value, and the signature algorithm identifier. I suggest that this be the API for all signature validation, and in the ES256 case, the SHA-256 have value can be computed inside the ES256_verify function.
The text was updated successfully, but these errors were encountered: