summaryrefslogtreecommitdiffstats
path: root/Lib/test/test_socket_ssl.py
diff options
context:
space:
mode:
authorJeremy Hylton <jeremy@alum.mit.edu>2001-10-18 00:28:50 (GMT)
committerJeremy Hylton <jeremy@alum.mit.edu>2001-10-18 00:28:50 (GMT)
commitde80f2efb5c189a9e709651af99e495b2a578b5a (patch)
treedc0eb0291bbd137b96cbb58f589279b2988083f9 /Lib/test/test_socket_ssl.py
parent5449e08412a5abd83c21d59764ef6240c58872b0 (diff)
downloadcpython-de80f2efb5c189a9e709651af99e495b2a578b5a.zip
cpython-de80f2efb5c189a9e709651af99e495b2a578b5a.tar.gz
cpython-de80f2efb5c189a9e709651af99e495b2a578b5a.tar.bz2
Expose three OpenSSL API calls for dealing with the PRNG.
Quoth the OpenSSL RAND_add man page: OpenSSL makes sure that the PRNG state is unique for each thread. On systems that provide /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(), RAND_egd(3) or RAND_load_file(3). I decided to expose RAND_add() because it's general and RAND_egd() because it's a useful special case. RAND_load_file() didn't seem to offer much over RAND_add(), so I skipped it. Also supplied RAND_status() which returns true if the PRNG is seeded and false if not.
Diffstat (limited to 'Lib/test/test_socket_ssl.py')
0 files changed, 0 insertions, 0 deletions