curl/tests/data/test879

<testcase>
<info>
<keywords>
POP3
SASL
SASL AUTH CRAM-MD5
SASL AUTH PLAIN
SASL DOWNGRADE
RFC1734
RFC2195
RFC5034
</keywords>
</info>

#
# Server-side
<reply>
<servercmd>
AUTH CRAM-MD5 PLAIN
REPLY "AUTH CRAM-MD5" + 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>
crypto
</features>
 <name>
POP3 CRAM-MD5 authentication with SASL downgrade
 </name>
 <command>
pop3://%HOSTIP:%POP3PORT/%TESTNUMBER -u user:secret
</command>
</client>

#
# Verify data after the test has been "shot"
<verify>
<protocol>
CAPA
AUTH CRAM-MD5
*
AUTH PLAIN
AHVzZXIAc2VjcmV0
RETR %TESTNUMBER
QUIT
</protocol>
</verify>
</testcase>
tests: Added POP3 SASL downgrade tests 2013-12-22 17:20:50 -05:00			`<testcase>`
			`<info>`
			`<keywords>`
			`POP3`
tests: Added "SASL" authentication keyword 2014-03-30 06:20:19 -04: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 07:01:15 -04:00			`SASL AUTH CRAM-MD5`
			`SASL AUTH PLAIN`
tests: made the SASL modes separate keywords 2014-03-15 06:13:13 -04:00			`SASL DOWNGRADE`
tests: Added POP3 SASL downgrade tests 2013-12-22 17:20:50 -05:00			`RFC1734`
			`RFC2195`
			`RFC5034`
			`</keywords>`
			`</info>`

			`#`
			`# Server-side`
			`<reply>`
			`<servercmd>`
			`AUTH CRAM-MD5 PLAIN`
			`REPLY "AUTH CRAM-MD5" + 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-18 16:54:35 -04:00			`REPLY AHVzZXIAc2VjcmV0 +OK Login successful`
tests: Added POP3 SASL downgrade tests 2013-12-22 17:20:50 -05:00			`</servercmd>`
			`<data>`
			`From: me@somewhere`
			`To: fake@nowhere`

			`body`

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

			`#`
			`# Client-side`
			`<client>`
			`<server>`
			`pop3`
			`</server>`
			`<features>`
			`crypto`
			`</features>`
			`<name>`
			`POP3 CRAM-MD5 authentication with SASL downgrade`
			`</name>`
			`<command>`
tests: use %TESTNUMBER instead of fixed number This makes the tests easier to copy and relocate to other test numbers without having to update content. Closes #6738 2021-03-12 11:38:26 -05:00			`pop3://%HOSTIP:%POP3PORT/%TESTNUMBER -u user:secret`
tests: Added POP3 SASL downgrade tests 2013-12-22 17:20:50 -05:00			`</command>`
			`</client>`

			`#`
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<protocol>`
			`CAPA`
			`AUTH CRAM-MD5`
			`*`
			`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-18 16:54:35 -04:00			`AHVzZXIAc2VjcmV0`
tests: use %TESTNUMBER instead of fixed number This makes the tests easier to copy and relocate to other test numbers without having to update content. Closes #6738 2021-03-12 11:38:26 -05:00			`RETR %TESTNUMBER`
tests: Added POP3 SASL downgrade tests 2013-12-22 17:20:50 -05:00			`QUIT`
			`</protocol>`
			`</verify>`
			`</testcase>`