Unlike crypto_sign_keypair() calls randombytes()
so it is not guaranteed to be thread-safe (for now).
This commit is contained in:
parent
732b7e1380
commit
63200794bf
@ -93,7 +93,8 @@ accordingly (both around `sodium_init()` and around other functions).
|
|||||||
Sodium also provides helper functions to generate random numbers,
|
Sodium also provides helper functions to generate random numbers,
|
||||||
leveraging `/dev/urandom` or `/dev/random` on *nix and the cryptographic
|
leveraging `/dev/urandom` or `/dev/random` on *nix and the cryptographic
|
||||||
service provider on Windows. The interface is similar to
|
service provider on Windows. The interface is similar to
|
||||||
`arc4random(3)`. It is `fork(2)`-safe but not thread-safe.
|
`arc4random(3)`. It is `fork(2)`-safe but not thread-safe. This holds
|
||||||
|
true for `crypto_sign_keypair()` as well.
|
||||||
|
|
||||||
uint32_t randombytes_random(void);
|
uint32_t randombytes_random(void);
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user