curl/tests/data/test873

<testcase>
<info>
<keywords>
POP3
SASL
SASL AUTH NTLM
SASL-IR
RFC1734
RFC5034
</keywords>
</info>

#
# Server-side
<reply>
<servercmd>
AUTH NTLM
REPLY AUTH + TlRMTVNTUAACAAAAAgACADAAAACGggEAc51AYVDgyNcAAAAAAAAAAG4AbgAyAAAAQ0MCAAQAQwBDAAEAEgBFAEwASQBTAEEAQgBFAFQASAAEABgAYwBjAC4AaQBjAGUAZABlAHYALgBuAHUAAwAsAGUAbABpAHMAYQBiAGUAdABoAC4AYwBjAC4AaQBjAGUAZABlAHYALgBuAHUAAAAAAA==
REPLY TlRMTVNTUAADAAAAGAAYAEAAAAAYABgAWAAAAAAAAABwAAAACAAIAHAAAAAIAAgAeAAAAAAAAAAAAAAAhoIBADQzMjE1MzIxAAAAAAAAAAAAAAAAAAAAADj3hs3u3j0kgJqCrLM+74BmaoNHDfIJjHRlc3R1c2VyY3VybGhvc3Q= +OK Login successful
</servercmd>
<data>
From: me@somewhere
To: fake@nowhere

body

--
  yours sincerely
</data>
</reply>

#
# Client-side
<client>
<server>
pop3
</server>
<features>
NTLM
SSL
!SSPI
debug
</features>
 <name>
POP3 NTLM authentication with initial response
 </name>
 <setenv>
# we force our own host name, in order to make the test machine independent
CURL_GETHOSTNAME=curlhost
# we try to use the LD_PRELOAD hack, if not a debug build
LD_PRELOAD=%PWD/libtest/.libs/libhostname.so
 </setenv>
 <command>
pop3://%HOSTIP:%POP3PORT/873 -u testuser:testpass --sasl-ir
</command>
<precheck>
chkhostname curlhost
</precheck>
</client>

#
# Verify data after the test has been "shot"
<verify>
<protocol>
CAPA
AUTH NTLM TlRMTVNTUAABAAAABoIIAAAAAAAAAAAAAAAAAAAAAAA=
TlRMTVNTUAADAAAAGAAYAEAAAAAYABgAWAAAAAAAAABwAAAACAAIAHAAAAAIAAgAeAAAAAAAAAAAAAAAhoIBADQzMjE1MzIxAAAAAAAAAAAAAAAAAAAAADj3hs3u3j0kgJqCrLM+74BmaoNHDfIJjHRlc3R1c2VyY3VybGhvc3Q=
RETR 873
QUIT
</protocol>
</verify>
</testcase>
tests: Added POP3 NTLM authentication with initial response test 2013-11-13 08:23:03 +08:00			`<testcase>`
			`<info>`
			`<keywords>`
			`POP3`
tests: Added "SASL" authentication keyword 2014-03-30 18:20:19 +08:00			`SASL`
tests: Replaced email authentication keywords with SASL based keywords 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 19:01:15 +08:00			`SASL AUTH NTLM`
tests: made the SASL modes separate keywords 2014-03-15 18:13:13 +08:00			`SASL-IR`
tests: Added POP3 NTLM authentication with initial response test 2013-11-13 08:23:03 +08:00			`RFC1734`
			`RFC5034`
			`</keywords>`
			`</info>`

			`#`
			`# Server-side`
			`<reply>`
			`<servercmd>`
			`AUTH NTLM`
ntlm: update selection of type 3 response 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 2018-12-28 22:04:53 +08:00			`REPLY AUTH + TlRMTVNTUAACAAAAAgACADAAAACGggEAc51AYVDgyNcAAAAAAAAAAG4AbgAyAAAAQ0MCAAQAQwBDAAEAEgBFAEwASQBTAEEAQgBFAFQASAAEABgAYwBjAC4AaQBjAGUAZABlAHYALgBuAHUAAwAsAGUAbABpAHMAYQBiAGUAdABoAC4AYwBjAC4AaQBjAGUAZABlAHYALgBuAHUAAAAAAA==`
			`REPLY TlRMTVNTUAADAAAAGAAYAEAAAAAYABgAWAAAAAAAAABwAAAACAAIAHAAAAAIAAgAeAAAAAAAAAAAAAAAhoIBADQzMjE1MzIxAAAAAAAAAAAAAAAAAAAAADj3hs3u3j0kgJqCrLM+74BmaoNHDfIJjHRlc3R1c2VyY3VybGhvc3Q= +OK Login successful`
tests: Added POP3 NTLM authentication with initial response test 2013-11-13 08:23:03 +08:00			`</servercmd>`
			`<data>`
			`From: me@somewhere`
			`To: fake@nowhere`

			`body`

			`--`
			`yours sincerely`
			`</data>`
			`</reply>`

			`#`
			`# Client-side`
			`<client>`
			`<server>`
			`pop3`
			`</server>`
			`<features>`
			`NTLM`
tests: Change NTLM tests to require SSL 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-12-30 04:23:25 +08:00			`SSL`
tests: Disabled NTLM tests when running with SSPI enabled 2013-12-29 04:22:22 +08:00			`!SSPI`
tests: Disabled NTLM tests for non-debug builds 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-06-12 01:12:48 +08:00			`debug`
tests: Added POP3 NTLM authentication with initial response test 2013-11-13 08:23:03 +08:00			`</features>`
			`<name>`
			`POP3 NTLM authentication with initial response`
			`</name>`
			`<setenv>`
			`# we force our own host name, in order to make the test machine independent`
			`CURL_GETHOSTNAME=curlhost`
			`# we try to use the LD_PRELOAD hack, if not a debug build`
			`LD_PRELOAD=%PWD/libtest/.libs/libhostname.so`
			`</setenv>`
			`<command>`
			`pop3://%HOSTIP:%POP3PORT/873 -u testuser:testpass --sasl-ir`
			`</command>`
			`<precheck>`
			`chkhostname curlhost`
			`</precheck>`
			`</client>`

			`#`
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<protocol>`
			`CAPA`
			`AUTH NTLM TlRMTVNTUAABAAAABoIIAAAAAAAAAAAAAAAAAAAAAAA=`
ntlm: update selection of type 3 response 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 2018-12-28 22:04:53 +08:00			`TlRMTVNTUAADAAAAGAAYAEAAAAAYABgAWAAAAAAAAABwAAAACAAIAHAAAAAIAAgAeAAAAAAAAAAAAAAAhoIBADQzMjE1MzIxAAAAAAAAAAAAAAAAAAAAADj3hs3u3j0kgJqCrLM+74BmaoNHDfIJjHRlc3R1c2VyY3VybGhvc3Q=`
tests: Added POP3 NTLM authentication with initial response test 2013-11-13 08:23:03 +08:00			`RETR 873`
			`QUIT`
			`</protocol>`
			`</verify>`
			`</testcase>`