aboutsummaryrefslogtreecommitdiff
path: root/tor-spec.txt
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2011-09-21 14:02:02 -0400
committerNick Mathewson <nickm@torproject.org>2011-09-21 14:02:02 -0400
commit5dafc783b0732faa2b866caa81d0b4b680d31ed1 (patch)
tree4a66324b09a3b4922e69023c363fbc46e6b55625 /tor-spec.txt
parent8d51fb27adcddca401a7d77c5b69bc25a199adaa (diff)
downloadtorspec-5dafc783b0732faa2b866caa81d0b4b680d31ed1.tar.gz
torspec-5dafc783b0732faa2b866caa81d0b4b680d31ed1.zip
Tighten up what tor-spec means by "random".
Diffstat (limited to 'tor-spec.txt')
-rw-r--r--tor-spec.txt5
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: