Setting `CURL_ENTROPY` in debug-enabled builds overrides the code paths
responsible for random number generation. To avoid masking issue there,
this patch moves `CURL_ENTROPY` settings to each test that requires it,
and stop setting it by default for all tests (in `runner.pm`).
This makes it possible to catch random generator issues in debug-enabled
builds; extending test coverage.
To keep offering a well-defined state for tests, make `runner.pm` delete
the `CURL_ENTROPY` env, if present.
Ref: #17970
Closes #17971
crypto
aws
</features>
+<setenv>
+CURL_ENTROPY=12345678
+</setenv>
<name>
HTTP AWS_SIGV4 for AWS S3: MIMEPOST
#
# Client-side
<client>
-# for the forced CURL_ENTROPY
+# require Debug for the forced CURL_ENTROPY
<features>
Debug
ws
</features>
+<setenv>
+CURL_ENTROPY=12345678
+</setenv>
<server>
http
</server>
Debug
ws
</features>
+<setenv>
+CURL_ENTROPY=12345678
+</setenv>
<server>
http
</server>
Debug
ws
</features>
+<setenv>
+CURL_ENTROPY=12345678
+</setenv>
<server>
http
</server>
Debug
ws
</features>
+<setenv>
+CURL_ENTROPY=12345678
+</setenv>
<server>
http
</server>
Debug
ws
</features>
+<setenv>
+CURL_ENTROPY=12345678
+</setenv>
<server>
http
</server>
crypto
digest
</features>
+<setenv>
+CURL_ENTROPY=12345678
+</setenv>
<name>
IMAP DIGEST-MD5 authentication
</name>
crypto
digest
</features>
+<setenv>
+CURL_ENTROPY=12345678
+</setenv>
<name>
POP3 DIGEST-MD5 authentication
</name>
crypto
digest
</features>
+<setenv>
+CURL_ENTROPY=12345678
+</setenv>
<name>
SMTP DIGEST-MD5 authentication
</name>
# enable memory debugging if curl is compiled with it
$ENV{'CURL_MEMDEBUG'} = "$logdir/$MEMDUMP";
- $ENV{'CURL_ENTROPY'}="12345678";
+ delete $ENV{'CURL_ENTROPY'} if($ENV{'CURL_ENTROPY'});
$ENV{'CURL_FORCETIME'}=1; # for debug NTLM magic
$ENV{'CURL_GLOBAL_INIT'}=1; # debug curl_global_init/cleanup use
$ENV{'HOME'}=$pwd;