ossl_seed: no more RAND_screen

RAND_screen() is slow, not thread-safe and not needed anymore since OpenSSL
uses the thread-safe win32 CryptoAPI nowadays.
This commit is contained in:
Daniel Stenberg
2010-12-23 14:36:07 +01:00
parent be16b227b7
commit 2dded8fedb

View File

@@ -225,7 +225,8 @@ static int ossl_seed(struct SessionHandle *data)
/* If we get here, it means we need to seed the PRNG using a "silly" /* If we get here, it means we need to seed the PRNG using a "silly"
approach! */ approach! */
#ifdef HAVE_RAND_SCREEN #ifdef HAVE_RAND_SCREEN
/* if RAND_screen() is present, it was called during global init */ /* if RAND_screen() is present, this is windows and thus we assume that the
randomness is already taken care of */
nread = 100; /* just a value */ nread = 100; /* just a value */
#else #else
{ {
@@ -685,13 +686,6 @@ int Curl_ossl_init(void)
OpenSSL_add_all_algorithms(); OpenSSL_add_all_algorithms();
#ifdef HAVE_RAND_SCREEN
/* This one gets a random value by reading the currently shown screen.
RAND_screen() is not thread-safe according to OpenSSL devs - although not
mentioned in documentation. */
RAND_screen();
#endif
return 1; return 1;
} }