-
Notifications
You must be signed in to change notification settings - Fork 2
Open
Labels
enhancementNew feature or requestNew feature or request
Description
It looks like PQClean adds an alternative "non-detached" signature mode
- https://github.com/PQClean/PQClean/blob/3b43bc6fe46fe47be38f87af5019a7f1462ae6dd/crypto_sign/dilithium3/clean/sign.c#L185
- https://github.com/PQClean/PQClean/blob/3b43bc6fe46fe47be38f87af5019a7f1462ae6dd/crypto_sign/falcon-512/clean/pqclean.c#L318
- https://github.com/PQClean/PQClean/blob/3b43bc6fe46fe47be38f87af5019a7f1462ae6dd/crypto_sign/sphincs-shake-128f-simple/clean/sign.c#L243
The API there looks a little weird
- returns
intindicating success/failure uint8_t *smwhich is a pre-allocated array ofmlen + CRYPTO_BYTESbytes, which the result will be written intosize_t *smlenwhich is a pre-allocated pointer, which(*mlen) + siglenwill be written into- This is, of course, only useful when
siglen < CRYPTO_BYTESmay occur, (i.e. variable-length signatures.)
- This is, of course, only useful when
const uint8_t *m, which is the array containing the message.- When
sm == m, then I guess that allows big efficiency gains withmemmove? (Does that mean we can reasonably deduce that the signature is always appended to the message?)
- When
size_t mlen, which is, of course, the length of the messageconst uint8_t sk[CRYPTO_SECRETKEYBYTES]
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or request