curl/tests/data/test880

<testcase>
<info>
<keywords>
POP3
SASL
SASL AUTH NTLM
SASL AUTH PLAIN
SASL DOWNGRADE
RFC1734
RFC5034
</keywords>
</info>

#
# Server-side
<reply>
<servercmd>
AUTH NTLM PLAIN
REPLY "AUTH NTLM" +
REPLY TlRMTVNTUAABAAAABoIIAAAAAAAAAAAAAAAAAAAAAAA= + Rubbish
REPLY * -ERR AUTH exchange cancelled by client
REPLY "AUTH PLAIN" +
REPLY AHVzZXIAc2VjcmV0 +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
</features>
 <name>
POP3 NTLM authentication with SASL downgrade
 </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/880 -u user:secret
</command>
<precheck>
chkhostname curlhost
</precheck>
</client>

#
# Verify data after the test has been "shot"
<verify>
<protocol>
CAPA
AUTH NTLM
TlRMTVNTUAABAAAABoIIAAAAAAAAAAAAAAAAAAAAAAA=
*
AUTH PLAIN
AHVzZXIAc2VjcmV0
RETR 880
QUIT
</protocol>
</verify>
</testcase>
tests: Added POP3 SASL downgrade tests 2013-12-23 06:20:50 +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`
			`SASL AUTH PLAIN`
tests: made the SASL modes separate keywords 2014-03-15 18:13:13 +08:00			`SASL DOWNGRADE`
tests: Added POP3 SASL downgrade tests 2013-12-23 06:20:50 +08:00			`RFC1734`
			`RFC5034`
			`</keywords>`
			`</info>`

			`#`
			`# Server-side`
			`<reply>`
			`<servercmd>`
			`AUTH NTLM PLAIN`
			`REPLY "AUTH NTLM" +`
			`REPLY TlRMTVNTUAABAAAABoIIAAAAAAAAAAAAAAAAAAAAAAA= + Rubbish`
			`REPLY * -ERR AUTH exchange cancelled by client`
			`REPLY "AUTH PLAIN" +`
sasl: Don't send authcid as authzid for the PLAIN mechanism as per RFC 4616 RFC 4616 specifies the authzid is optional in the client authentication message and that the server will derive the authorisation identity (authzid) from the authentication identity (authcid) when not specified by the client. 2019-04-19 04:54:35 +08:00			`REPLY AHVzZXIAc2VjcmV0 +OK Login successful`
tests: Added POP3 SASL downgrade tests 2013-12-23 06:20:50 +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: Added POP3 SASL downgrade tests 2013-12-23 06:20:50 +08:00			`</features>`
			`<name>`
			`POP3 NTLM authentication with SASL downgrade`
			`</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/880 -u user:secret`
			`</command>`
			`<precheck>`
			`chkhostname curlhost`
			`</precheck>`
			`</client>`

			`#`
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<protocol>`
			`CAPA`
			`AUTH NTLM`
			`TlRMTVNTUAABAAAABoIIAAAAAAAAAAAAAAAAAAAAAAA=`
			`*`
			`AUTH PLAIN`
sasl: Don't send authcid as authzid for the PLAIN mechanism as per RFC 4616 RFC 4616 specifies the authzid is optional in the client authentication message and that the server will derive the authorisation identity (authzid) from the authentication identity (authcid) when not specified by the client. 2019-04-19 04:54:35 +08:00			`AHVzZXIAc2VjcmV0`
tests: Added POP3 SASL downgrade tests 2013-12-23 06:20:50 +08:00			`RETR 880`
			`QUIT`
			`</protocol>`
			`</verify>`
			`</testcase>`