[tor-commits] [torspec/master] Tighten up what tor-spec means by "random".
nickm at torproject.org
nickm at torproject.org
Wed Sep 21 17:59:55 UTC 2011
commit 5dafc783b0732faa2b866caa81d0b4b680d31ed1
Author: Nick Mathewson <nickm at torproject.org>
Date: Wed Sep 21 14:02:02 2011 -0400
Tighten up what tor-spec means by "random".
---
tor-spec.txt | 5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/tor-spec.txt b/tor-spec.txt
index 7998946..48cdd94 100644
--- a/tor-spec.txt
+++ b/tor-spec.txt
@@ -96,8 +96,9 @@ see tor-design.pdf.
When we refer to "the hash of a public key", we mean the SHA-1 hash of the
DER encoding of an ASN.1 RSA public key (as specified in PKCS.1).
- All "random" values should be generated with a cryptographically strong
- random number generator, unless otherwise noted.
+ All "random" values MUST be generated with a cryptographically
+ strong pseudorandom number generator seeded from a strong entropy
+ source, unless otherwise noted.
The "hybrid encryption" of a byte sequence M with a public key PK is
computed as follows:
More information about the tor-commits
mailing list