diff options
Diffstat (limited to 'src')
| -rw-r--r-- | src/lib/libcrypto/doc/RAND_bytes.pod | 12 | ||||
| -rw-r--r-- | src/lib/libssl/src/doc/crypto/RAND_bytes.pod | 12 |
2 files changed, 6 insertions, 18 deletions
diff --git a/src/lib/libcrypto/doc/RAND_bytes.pod b/src/lib/libcrypto/doc/RAND_bytes.pod index 34c945b4e5..c89961ada3 100644 --- a/src/lib/libcrypto/doc/RAND_bytes.pod +++ b/src/lib/libcrypto/doc/RAND_bytes.pod | |||
| @@ -15,8 +15,7 @@ RAND_bytes, RAND_pseudo_bytes - generate random data | |||
| 15 | =head1 DESCRIPTION | 15 | =head1 DESCRIPTION |
| 16 | 16 | ||
| 17 | RAND_bytes() puts B<num> cryptographically strong pseudo-random bytes | 17 | RAND_bytes() puts B<num> cryptographically strong pseudo-random bytes |
| 18 | into B<buf>. An error occurs if the PRNG has not been seeded with | 18 | into B<buf>. |
| 19 | enough randomness to ensure an unpredictable byte sequence. | ||
| 20 | 19 | ||
| 21 | RAND_pseudo_bytes() puts B<num> pseudo-random bytes into B<buf>. | 20 | RAND_pseudo_bytes() puts B<num> pseudo-random bytes into B<buf>. |
| 22 | Pseudo-random byte sequences generated by RAND_pseudo_bytes() will be | 21 | 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 | |||
| 25 | certain purposes in cryptographic protocols, but usually not for key | 24 | certain purposes in cryptographic protocols, but usually not for key |
| 26 | generation etc. | 25 | generation etc. |
| 27 | 26 | ||
| 28 | The contents of B<buf> is mixed into the entropy pool before retrieving | ||
| 29 | the new pseudo-random bytes unless disabled at compile time (see FAQ). | ||
| 30 | |||
| 31 | =head1 RETURN VALUES | 27 | =head1 RETURN VALUES |
| 32 | 28 | ||
| 33 | RAND_bytes() returns 1 on success, 0 otherwise. The error code can be obtained | 29 | RAND_bytes() returns 1. |
| 34 | by L<ERR_get_error(3)|ERR_get_error(3)>. RAND_pseudo_bytes() returns 1 if the | 30 | RAND_pseudo_bytes() returns 1. |
| 35 | bytes generated are cryptographically strong, 0 otherwise. Both functions | ||
| 36 | return -1 if they are not supported by the current RAND method. | ||
| 37 | 31 | ||
| 38 | =head1 SEE ALSO | 32 | =head1 SEE ALSO |
| 39 | 33 | ||
diff --git a/src/lib/libssl/src/doc/crypto/RAND_bytes.pod b/src/lib/libssl/src/doc/crypto/RAND_bytes.pod index 34c945b4e5..c89961ada3 100644 --- a/src/lib/libssl/src/doc/crypto/RAND_bytes.pod +++ b/src/lib/libssl/src/doc/crypto/RAND_bytes.pod | |||
| @@ -15,8 +15,7 @@ RAND_bytes, RAND_pseudo_bytes - generate random data | |||
| 15 | =head1 DESCRIPTION | 15 | =head1 DESCRIPTION |
| 16 | 16 | ||
| 17 | RAND_bytes() puts B<num> cryptographically strong pseudo-random bytes | 17 | RAND_bytes() puts B<num> cryptographically strong pseudo-random bytes |
| 18 | into B<buf>. An error occurs if the PRNG has not been seeded with | 18 | into B<buf>. |
| 19 | enough randomness to ensure an unpredictable byte sequence. | ||
| 20 | 19 | ||
| 21 | RAND_pseudo_bytes() puts B<num> pseudo-random bytes into B<buf>. | 20 | RAND_pseudo_bytes() puts B<num> pseudo-random bytes into B<buf>. |
| 22 | Pseudo-random byte sequences generated by RAND_pseudo_bytes() will be | 21 | 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 | |||
| 25 | certain purposes in cryptographic protocols, but usually not for key | 24 | certain purposes in cryptographic protocols, but usually not for key |
| 26 | generation etc. | 25 | generation etc. |
| 27 | 26 | ||
| 28 | The contents of B<buf> is mixed into the entropy pool before retrieving | ||
| 29 | the new pseudo-random bytes unless disabled at compile time (see FAQ). | ||
| 30 | |||
| 31 | =head1 RETURN VALUES | 27 | =head1 RETURN VALUES |
| 32 | 28 | ||
| 33 | RAND_bytes() returns 1 on success, 0 otherwise. The error code can be obtained | 29 | RAND_bytes() returns 1. |
| 34 | by L<ERR_get_error(3)|ERR_get_error(3)>. RAND_pseudo_bytes() returns 1 if the | 30 | RAND_pseudo_bytes() returns 1. |
| 35 | bytes generated are cryptographically strong, 0 otherwise. Both functions | ||
| 36 | return -1 if they are not supported by the current RAND method. | ||
| 37 | 31 | ||
| 38 | =head1 SEE ALSO | 32 | =head1 SEE ALSO |
| 39 | 33 | ||
