Re: Change in allowplaintext behaviour in 2.3.9?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Quoting Nels Lindquist (nlindq@xxxxxxx):
> Hi there.
> 
> I understand that the default for "allowplaintext" is now off in 2.3.9,
> which seems like a perfectly fine change.
> 
> However, I'm also noticing a behavioural change when allowplaintext is
> enabled.
> 
> With 2.3.8 and "allowplaintext" on, PLAIN and LOGIN methods were only
> explicitly offered when a secure connection was present.  I've upgraded
> to 2.3.9 (via Simon's RPM) and now "AUTH=PLAIN AUTH=LOGIN" are
> immediately offered even when no TLS/SSL encryption is enabled.
> 
> Was this an intentional change?
> 

Thos fixes another allowplaintext: 1 problem.

    /* authstate already created by mysasl_proxy_policy() */
    /* Not when using login and allowplaintext.  imapd_authstate is NULL
    */
    if (imapd_authstate == NULL)
        imapd_authstate = auth_newstate(imapd_userid);

With allowplaintext: 1 a user can login but access to the mailbox is denied.

John Capo

----
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

[Index of Archives]     [Cyrus SASL]     [Squirrel Mail]     [Asterisk PBX]     [Video For Linux]     [Photo]     [Yosemite News]     [gtk]     [KDE]     [Gimp on Windows]     [Steve's Art]

  Powered by Linux