Fix documentation for Dilithium crypto_sign_open

It mentioned `sk` instead of `pk` as specified in the arguments.

Closes #205.
This commit is contained in:
Thom Wiggers 2019-07-22 09:20:54 +02:00
parent ef62745846
commit 3c2967b5a1
No known key found for this signature in database
GPG Key ID: 001BB0A7CE26E363
3 changed files with 3 additions and 3 deletions

View File

@ -367,7 +367,7 @@ int PQCLEAN_DILITHIUM2_CLEAN_crypto_sign(uint8_t *sm,
* - unsigned long long *mlen: pointer to output length of message
* - const unsigned char *sm: pointer to signed message
* - unsigned long long smlen: length of signed message
* - const unsigned char *sk: pointer to bit-packed public key
* - const unsigned char *pk: pointer to bit-packed public key
*
* Returns 0 if signed message could be verified correctly and -1 otherwise
**************************************************/

View File

@ -367,7 +367,7 @@ int PQCLEAN_DILITHIUM3_CLEAN_crypto_sign(uint8_t *sm,
* - unsigned long long *mlen: pointer to output length of message
* - const unsigned char *sm: pointer to signed message
* - unsigned long long smlen: length of signed message
* - const unsigned char *sk: pointer to bit-packed public key
* - const unsigned char *pk: pointer to bit-packed public key
*
* Returns 0 if signed message could be verified correctly and -1 otherwise
**************************************************/

View File

@ -367,7 +367,7 @@ int PQCLEAN_DILITHIUM4_CLEAN_crypto_sign(uint8_t *sm,
* - unsigned long long *mlen: pointer to output length of message
* - const unsigned char *sm: pointer to signed message
* - unsigned long long smlen: length of signed message
* - const unsigned char *sk: pointer to bit-packed public key
* - const unsigned char *pk: pointer to bit-packed public key
*
* Returns 0 if signed message could be verified correctly and -1 otherwise
**************************************************/