2000-01-22 01:50:27 +08:00
|
|
|
=pod
|
|
|
|
|
|
|
|
=head1 NAME
|
|
|
|
|
2000-02-24 19:55:57 +08:00
|
|
|
rand - pseudo-random number generator
|
2000-01-22 01:50:27 +08:00
|
|
|
|
|
|
|
=head1 SYNOPSIS
|
|
|
|
|
|
|
|
#include <openssl/rand.h>
|
|
|
|
|
2002-08-06 00:27:01 +08:00
|
|
|
int RAND_set_rand_engine(ENGINE *engine);
|
|
|
|
|
2001-03-21 23:25:56 +08:00
|
|
|
int RAND_bytes(unsigned char *buf, int num);
|
|
|
|
int RAND_pseudo_bytes(unsigned char *buf, int num);
|
2000-01-22 01:50:27 +08:00
|
|
|
|
2001-03-21 23:25:56 +08:00
|
|
|
void RAND_seed(const void *buf, int num);
|
|
|
|
void RAND_add(const void *buf, int num, int entropy);
|
2000-02-24 10:51:47 +08:00
|
|
|
int RAND_status(void);
|
2000-01-22 01:50:27 +08:00
|
|
|
|
2001-03-21 23:25:56 +08:00
|
|
|
int RAND_load_file(const char *file, long max_bytes);
|
2000-01-22 01:50:27 +08:00
|
|
|
int RAND_write_file(const char *file);
|
2001-03-21 23:25:56 +08:00
|
|
|
const char *RAND_file_name(char *file, size_t num);
|
2000-01-22 01:50:27 +08:00
|
|
|
|
2000-02-24 10:51:47 +08:00
|
|
|
int RAND_egd(const char *path);
|
|
|
|
|
2002-08-06 00:27:01 +08:00
|
|
|
void RAND_set_rand_method(const RAND_METHOD *meth);
|
|
|
|
const RAND_METHOD *RAND_get_rand_method(void);
|
2015-10-28 01:40:11 +08:00
|
|
|
RAND_METHOD *RAND_OpenSSL(void);
|
2000-01-22 01:50:27 +08:00
|
|
|
|
|
|
|
void RAND_cleanup(void);
|
|
|
|
|
2002-08-06 00:27:01 +08:00
|
|
|
/* For Win32 only */
|
|
|
|
void RAND_screen(void);
|
|
|
|
int RAND_event(UINT, WPARAM, LPARAM);
|
|
|
|
|
2000-01-22 01:50:27 +08:00
|
|
|
=head1 DESCRIPTION
|
|
|
|
|
2002-08-06 00:27:01 +08:00
|
|
|
Since the introduction of the ENGINE API, the recommended way of controlling
|
|
|
|
default implementations is by using the ENGINE API functions. The default
|
|
|
|
B<RAND_METHOD>, as set by RAND_set_rand_method() and returned by
|
|
|
|
RAND_get_rand_method(), is only used if no ENGINE has been set as the default
|
2013-09-06 04:43:50 +08:00
|
|
|
"rand" implementation. Hence, these two functions are no longer the recommended
|
2002-08-06 00:27:01 +08:00
|
|
|
way to control defaults.
|
|
|
|
|
|
|
|
If an alternative B<RAND_METHOD> implementation is being used (either set
|
|
|
|
directly or as provided by an ENGINE module), then it is entirely responsible
|
|
|
|
for the generation and management of a cryptographically secure PRNG stream. The
|
|
|
|
mechanisms described below relate solely to the software PRNG implementation
|
|
|
|
built in to OpenSSL and used by default.
|
|
|
|
|
2000-01-22 01:50:27 +08:00
|
|
|
These functions implement a cryptographically secure pseudo-random
|
|
|
|
number generator (PRNG). It is used by other library functions for
|
|
|
|
example to generate random keys, and applications can use it when they
|
|
|
|
need randomness.
|
|
|
|
|
|
|
|
A cryptographic PRNG must be seeded with unpredictable data such as
|
|
|
|
mouse movements or keys pressed at random by the user. This is
|
2015-08-18 03:21:33 +08:00
|
|
|
described in L<RAND_add(3)>. Its state can be saved in a seed file
|
|
|
|
(see L<RAND_load_file(3)>) to avoid having to go through the
|
2000-01-27 09:25:31 +08:00
|
|
|
seeding process whenever the application is started.
|
2000-01-22 01:50:27 +08:00
|
|
|
|
2015-08-18 03:21:33 +08:00
|
|
|
L<RAND_bytes(3)> describes how to obtain random data from the
|
2000-01-27 09:25:31 +08:00
|
|
|
PRNG.
|
2000-01-22 01:50:27 +08:00
|
|
|
|
|
|
|
=head1 SEE ALSO
|
|
|
|
|
2015-08-18 03:21:33 +08:00
|
|
|
L<BN_rand(3)>, L<RAND_add(3)>,
|
|
|
|
L<RAND_load_file(3)>, L<RAND_egd(3)>,
|
|
|
|
L<RAND_bytes(3)>,
|
|
|
|
L<RAND_set_rand_method(3)>,
|
|
|
|
L<RAND_cleanup(3)>
|
2000-01-22 01:50:27 +08:00
|
|
|
|
|
|
|
=cut
|