You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Prevent AUTHENTICATE without matching AUTH=#{mechanism} capability #48
changed the title [-]honor server capabilities (many servers disallow unless TLS is established)[/-][+]honor LOGINDISABLED and AUTH=mechanism capabilities[/+]on Nov 23, 2021
changed the title [-]honor AUTH=mechanism capabilities[/-][+]Prevent `SASL` mechanisms that aren't listed in server's AUTH= capabilities[/+]on Nov 23, 2021
changed the title [-]Prevent `SASL` mechanisms that aren't listed in server's AUTH= capabilities[/-][+]Prevent `AUTHENTICATE` without matching `AUTH={mechanism}` capability[/+]on Feb 17, 2023
changed the title [-]Prevent `AUTHENTICATE` without matching `AUTH={mechanism}` capability[/-][+]Prevent `AUTHENTICATE` without matching `AUTH=#{mechanism}` capability[/+]on Feb 17, 2023
While working on SASL-IR, I looked more closely at the RFCs. And the specs do not treat AUTH={mechanism} as identical to LOGINDISABLED:
LOGINDISABLED is a negative requirement on the client (MUST NOT login)
AUTH={mechanism} is a positive suggestion to the server (SHOULD advertise allowed mechanisms).
SASL has an important benefit over login: we can ask server if it's okay to proceed prior to sending any sensitive data. As such, I made the decision in #90 to still support calling authenticate with any mechanism without any warnings, however this has the important caveat that the initial response is only sent when the mechanism is advertised.
Activity
[-]honor server capabilities (many servers disallow unless TLS is established)[/-][+]honor LOGINDISABLED and AUTH=mechanism capabilities[/+][-]honor LOGINDISABLED and AUTH=mechanism capabilities[/-][+]honor AUTH=mechanism capabilities[/+][-]honor AUTH=mechanism capabilities[/-][+]Prevent `SASL` mechanisms that aren't listed in server's AUTH= capabilities[/+][-]Prevent `SASL` mechanisms that aren't listed in server's AUTH= capabilities[/-][+]Prevent `AUTHENTICATE` without matching `AUTH={mechanism}` capability[/+][-]Prevent `AUTHENTICATE` without matching `AUTH={mechanism}` capability[/-][+]Prevent `AUTHENTICATE` without matching `AUTH=#{mechanism}` capability[/+]nevans commentedon Sep 25, 2023
While working on SASL-IR, I looked more closely at the RFCs. And the specs do not treat
AUTH={mechanism}as identical toLOGINDISABLED:LOGINDISABLEDis a negative requirement on the client (MUST NOT login)AUTH={mechanism}is a positive suggestion to the server (SHOULD advertise allowed mechanisms).SASL has an important benefit over
login: we can ask server if it's okay to proceed prior to sending any sensitive data. As such, I made the decision in #90 to still support calling authenticate with any mechanism without any warnings, however this has the important caveat that the initial response is only sent when the mechanism is advertised.net-imap/lib/net/imap.rb
Lines 1077 to 1078 in aa0229a