summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTed Unangst <tedu@cvs.openbsd.org>2014-05-30 02:29:39 +0000
committerTed Unangst <tedu@cvs.openbsd.org>2014-05-30 02:29:39 +0000
commit535191e7b98c791e3b5dd2e393164e1b0b7c6b04 (patch)
treebc1d8548f737f37ff3690a6b8012d62ab5359ec6
parentaf1afaf236c6d0745e382297f4b6c8c667be47fc (diff)
remove some of the bigger lies, as applicable to libressl.
-rw-r--r--lib/libcrypto/doc/RAND_bytes.pod12
1 files changed, 3 insertions, 9 deletions
diff --git a/lib/libcrypto/doc/RAND_bytes.pod b/lib/libcrypto/doc/RAND_bytes.pod
index 34c945b4e5d..c89961ada3d 100644
--- a/lib/libcrypto/doc/RAND_bytes.pod
+++ b/lib/libcrypto/doc/RAND_bytes.pod
@@ -15,8 +15,7 @@ RAND_bytes, RAND_pseudo_bytes - generate random data
=head1 DESCRIPTION
RAND_bytes() puts B<num> cryptographically strong pseudo-random bytes
-into B<buf>. An error occurs if the PRNG has not been seeded with
-enough randomness to ensure an unpredictable byte sequence.
+into B<buf>.
RAND_pseudo_bytes() puts B<num> pseudo-random bytes into B<buf>.
Pseudo-random byte sequences generated by RAND_pseudo_bytes() will be
@@ -25,15 +24,10 @@ unpredictable. They can be used for non-cryptographic purposes and for
certain purposes in cryptographic protocols, but usually not for key
generation etc.
-The contents of B<buf> is mixed into the entropy pool before retrieving
-the new pseudo-random bytes unless disabled at compile time (see FAQ).
-
=head1 RETURN VALUES
-RAND_bytes() returns 1 on success, 0 otherwise. The error code can be obtained
-by L<ERR_get_error(3)|ERR_get_error(3)>. RAND_pseudo_bytes() returns 1 if the
-bytes generated are cryptographically strong, 0 otherwise. Both functions
-return -1 if they are not supported by the current RAND method.
+RAND_bytes() returns 1.
+RAND_pseudo_bytes() returns 1.
=head1 SEE ALSO