Bug: https://github.com/bagder/curl/pull/105

No longer necessary after Michael Osipov's rework

After the fixed cookie lock deadlock, this test now passes and it
detects double-locking and double-unlocking of mutexes.

It's irrelevant to the test, and will change depending on which SSL
library is being used by libcurl.

This seems to have become necessary for SRP support to work starting
with GnuTLS ver. 2.99.0. Since support for SRP was added to GnuTLS
before the function that takes this priority string, there should be no
issue with backward compatibility.

These tests have been broken since commit 1958fe57 in Oct. 2011

This caused segfaults on tests 823 869 907.

Curl_rand() will return a dummy and repatable random value for this
case. Makes it possible to write test cases that verify output.

Also, fake timestamp with CURL_FORCETIME set.

Only when built debug enabled of course.

Curl_ssl_random() was not used anymore so it has been
removed. Curl_rand() is enough.

create_digest_md5_message: generate base64 instead of hex string

curl_sasl: also fix memory leaks in some OOM situations

Added required "debug" feature, missed in commit 1c9aaa0b, as NTLMv2
calls Curl_rand() which can only be fixed to a specific entropy in
debug builds.

gcc spit out warning: variable 'x' might be clobbered by 'longjmp' or
'vfork' messages for a few variables.  These automatic variables were
expected to be changed between a setjmp/longjmp and hold their values,
so are now marked volatile.

Follow-up to commit 121bcfee. curl-config --features now lists
GSS-API but it is not a listed feature in curl -V. This should probably
be synchronized.

Verifies that the change in 68f0166a works as intended and that
different HTTP auth credentials to the same host still re-uses the
connection properly.

In commit 0b3750b5 (released in 7.36.0) we fixed a timeout issue
but instead broke the timings.

To fix this, I introduce a new timestamp to use for the timeouts and
restored the previous timestamp and timestamp position so that the old
timer functionality is restored.

In addition to that, that change also broke connection timeouts for when
more than one connect was used (as it would then count the total time
from the first connect and not for the most recent one). Now
Curl_timeleft() has been modified so that it checks against different
start times depending on which timeout it checks.

Test 1303 is updated accordingly.

Bug: http://curl.haxx.se/mail/lib-2014-05/0147.html
Reported-by: Ryan Braud

Just to make sure the test is properly repeatable.

Bug: http://curl.haxx.se/mail/lib-2014-05/0081.html
Reported-by: Henrik

This allows a libcurl test to portably sleep for a given number of
milliseconds.

If the precision is indeed shorter than the string, don't strlen() to
find the end because that's not how the precision operator works.

I also added a unit test for curl_msnprintf to make sure this works and
that the fix doesn't a few other basic use cases. I found a POSIX
compliance problem that I marked TODO in the unit test, and I figure we
need to add more tests in the future.

Reported-by: Török Edwin