From: Tomas Mraz <tomas@openssl.org>
Date: Wed, 11 Oct 2023 09:20:02 +0000 (+0200)
Subject: Windows: use srand() instead of srandom()
X-Git-Tag: openssl-3.1.4~29
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=77ce9ea496f5bc8fc513082c74c207a3240febb0;p=thirdparty%2Fopenssl.git

Windows: use srand() instead of srandom()

This is used for memory allocation failure debugging only

Reviewed-by: Tom Cosgrove <tom.cosgrove@arm.com>
Reviewed-by: Paul Dale <pauli@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/22347)

(cherry picked from commit 3b107b86ca7d1c6309bc7071ead59acb8c098f3b)
---

diff --git a/crypto/mem.c b/crypto/mem.c
index 76779a461f1..cc19856771f 100644
--- a/crypto/mem.c
+++ b/crypto/mem.c
@@ -122,12 +122,13 @@ static void parseit(void)
 }
 
 /*
- * Windows doesn't have random(), but it has rand()
+ * Windows doesn't have random() and srandom(), but it has rand() and srand().
  * Some rand() implementations aren't good, but we're not
  * dealing with secure randomness here.
  */
 # ifdef _WIN32
 #  define random() rand()
+#  define srandom(seed) srand(seed)
 # endif
 /*
  * See if the current malloc should fail.