curl - cURL mirror with patches applied

Age	Commit message (Collapse)	Author
2019-12-31	tests: Change NTLM tests to require SSL	Jay Satiro
	Prior to this change tests that required NTLM feature did not require SSL feature. There are pending changes to cmake builds that will allow enabling NTLM in non-SSL builds in Windows. In that case the NTLM auth strings created are different from what is expected by the NTLM tests and they fail: "The issue with NTLM is that previous non-SSL builds would not enable NTLM and so the NTLM tests would be skipped." Assisted-by: marc-groundctl@users.noreply.github.com Ref: https://github.com/curl/curl/pull/4717#issuecomment-566218729 Closes https://github.com/curl/curl/pull/4768
2019-01-01	ntlm: update selection of type 3 response	Markus Moeller
	NTLM2 did not work i.e. no NTLMv2 response was created. Changing the check seems to work. Ref: https://winprotocoldoc.blob.core.windows.net/productionwindowsarchives/MS-NLMP/[MS-NLMP].pdf Fixes https://github.com/curl/curl/issues/3286 Closes https://github.com/curl/curl/pull/3287 Closes https://github.com/curl/curl/pull/3415
2017-05-08	tests: updated for modified fake random	Daniel Stenberg

2014-06-11	NTLM: set a fake entropy for debug builds with CURL_ENTROPY set	Daniel Stenberg
	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
2014-06-11	tests: Disabled NTLM tests for non-debug builds	Steve Holme
	Added required "debug" feature, missed in commit 1c9aaa0bac, as NTLMv2 calls Curl_rand() which can only be fixed to a specific entropy in debug builds.
2014-03-30	tests: Replaced email authentication keywords with SASL based keywords	Steve Holme
	As the email protocols implement SASL authentication rather than IMAP, POP3 and SMTP specific authentication, updated the authentication keywords to reflect this.
2014-03-30	tests: Added "SASL" authentication keyword	Steve Holme

2014-01-30	tests: Updated NTLM tests for NTLMv2 type-3 message	Steve Holme

2013-12-28	tests: Disabled NTLM tests when running with SSPI enabled	Steve Holme

2013-10-30	tests: use proper padding in NTLM responses	Kamil Dudka

2013-10-26	tests: Tidy up of SMTP and POP3 tests	Steve Holme
	Corrected line endings, RFC references and standardised on user names and passwords used in the tests.
2013-10-15	test906: Fixed failing test on some platforms	Steve Holme
	Bug: http://sourceforge.net/p/curl/bugs/1291 Reported-by: David Walser
2013-09-29	tests: Updated email addresses in SMTP tests following recent changes	Steve Holme

2013-09-29	ftpserver.pl: Moved specifying the test number from the RCPT address	Steve Holme
	...to the client address as this frees the RCPT strings to contain just an email address and by passing the test number into curl as the client address remains consistent with POP3 and IMAP tests as they are specified in the URL.
2013-09-23	test906: Fixed type-2 response	Steve Holme

2013-09-23	test906: Fixed type-1 message not handled error	Steve Holme
	...from commit f81d1e16664976 due to copy paste error.
2013-09-22	tests: Added SMTP AUTH NTLM test	Steve Holme

2013-09-22	tests: Regrouping of SMTP tests	Steve Holme

2013-09-22	tests: Fixed smtp rcpt to addresses	Steve Holme

2013-05-04	smtp: Fixed sending of double CRLF caused by first in EOB	Steve Holme
	If the mail sent during the transfer contains a terminating <CRLF> then we should not send the first <CRLF> of the EOB as specified in RFC-5321. Additionally don't send the <CRLF> if there is "no mail data" as the DATA command already includes it.
2013-04-28	tests: Corrected the SMTP tests to be RFC2821 compliant	Steve Holme
	The emails that are sent to the server during these tests were incorrectly formatted as they contained one or more LF terminated lines rather than being CRLF terminated as per Section 2.3.7 of RFC-2821. This wasn't a problem for the test suite as the <stdin> data matched the <upload> data but anyone using these tests as reference would be sending incorrect data to a server.
2013-03-10	email-tests: Updated the test data that corresponds to the test number	Steve Holme
	Finished segregating the email protocol tests, into their own protocol based ranges, in preparation of adding more e-mail related tests to the test suite.
2013-03-10	email-tests: Renamed the SMTP tests to be in the range 900-906	Steve Holme
	Continued segregating the email protocol tests, into their own protocol based ranges, in preparation of adding more e-mail related tests to the test suite.