11 Jan 2011 14:39
POP3 Authorization using SCRAM-SHA-1 fails
Steffen Lehmann <mpop <at> as-lehmann.de>
2011-01-11 13:39:12 GMT
2011-01-11 13:39:12 GMT
POP3 Authorization using SCRAM-SHA-1 fails, because mpop violates the rules according to SASL RFC 4422, Section 3: "Where the mechanism specifies that the server is to return additional data to the client with a successful outcome and this field is unavailable or unused, the additional data is sent as a challenge whose response is empty. After receiving this response, the server then indicates the successful outcome." RFC 5034, Section 4: "Note that POP3 does not allow for additional data to be sent with a message indicating a successfull outcome (see Section 3.6 of RFC 4422)." Hence, the following message sequence according to SASL RFC 4422, Section 3 applies: C: Request authentication exchange S: Initial challenge C: Initial response <additional challenge/response messages> S: Additional data challenge C: Empty Response S: Outcome of authentication exchange But mpop behaves as following: C: AUTH SCRAM-SHA-1 (POP3: command request) S: + (SASL: Initial challenge) C: biwsb... (SASL: Initial response; RFC 5802 client-first-message) S: + cj01b2t... (SASL: additional challenge; RFC 5802 server-(Continue reading)first- message)
RSS Feed