summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorUlf Möller <ulf@openssl.org>2000-02-25 15:43:33 +0000
committerUlf Möller <ulf@openssl.org>2000-02-25 15:43:33 +0000
commit1c890fa86415d7f739509701e213a2093fe53438 (patch)
tree485f6a3cce81ab47894b680df4c5333f2c8b8219
parentb08b07b8ae6c216390727ee6b39afc79c6589973 (diff)
mention RAND_egd()
-rw-r--r--doc/crypto/RAND_add.pod6
1 files changed, 4 insertions, 2 deletions
diff --git a/doc/crypto/RAND_add.pod b/doc/crypto/RAND_add.pod
index a3a2113cac..0a13ec2a92 100644
--- a/doc/crypto/RAND_add.pod
+++ b/doc/crypto/RAND_add.pod
@@ -34,7 +34,8 @@ passwords. The seed values cannot be recovered from the PRNG output.
OpenSSL makes sure that the PRNG state is unique for each thread. On
systems that provide C</dev/urandom>, the randomness device is used
to seed the PRNG transparently. However, on all other systems, the
-application is responsible for seeding the PRNG by calling RAND_add()
+application is responsible for seeding the PRNG by calling RAND_add(),
+L<RAND_egd(3)|RAND_egd(3)>
or L<RAND_load_file(3)|RAND_load_file(3)>.
RAND_seed() is equivalent to RAND_add() when B<num == entropy>.
@@ -55,7 +56,8 @@ The other functions do not return values.
=head1 SEE ALSO
-L<rand(3)|rand(3)>, L<RAND_load_file(3)|RAND_load_file(3)>, L<RAND_cleanup(3)|RAND_cleanup(3)>
+L<rand(3)|rand(3)>, L<RAND_egd(3)|RAND_egd(3)>,
+L<RAND_load_file(3)|RAND_load_file(3)>, L<RAND_cleanup(3)|RAND_cleanup(3)>
=head1 HISTORY