From 63200794bf20b9b1c45c624f92ccaa81931f619d Mon Sep 17 00:00:00 2001
From: Frank Denis <github@pureftpd.org>
Date: Fri, 26 Apr 2013 09:55:47 -0700
Subject: [PATCH] Unlike crypto_sign_keypair() calls randombytes() so it is not
 guaranteed to be thread-safe (for now).

---
 README.markdown | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/README.markdown b/README.markdown
index 35fbb470..0714325d 100644
--- a/README.markdown
+++ b/README.markdown
@@ -93,7 +93,8 @@ accordingly (both around `sodium_init()` and around other functions).
 Sodium also provides helper functions to generate random numbers,
 leveraging `/dev/urandom` or `/dev/random` on *nix and the cryptographic
 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);