#3862: Error in POP3 authentication via SASL mechanism DIGEST-MD5
-----------------------+----------------------
Reporter: g1pimutt | Owner: mutt-dev
Type: defect | Status: new
Priority: major | Milestone:
Component: POP | Version:
Resolution: | Keywords:
-----------------------+----------------------
Comment (by kevin8t8):
Sorry but this patch doesn't make sense to me. The sasl code should be
making the decisions about when the authentication is done and return that
via sasl_client_step(). The sasl_client_step() documentation even says:
{{{
It returns SASL_OK if the whole negotiation is successful
and SASL_CONTINUE if this step is ok but at least one more step is needed.
A client should not assume an authentication negotiation
is successful just because the server signaled success
via protocol (i.e. if the server said ". OK Authentication
succeeded" in IMAP sasl_client_step should still be called
one more time with a serverinlen of zero.
}}}
What return code are you seeing for the case where you are seeing it abort
after step 4?
--
Ticket URL: <https://dev.mutt.org/trac/ticket/3862#comment:3>
Mutt <http://www.mutt.org/>
The Mutt mail user agent