On 12/04/2012 10:34 AM, "Claas Kähler" <[email protected]>" wrote:
> But if i use plaintext for the > encryption the userauthentication failed. There is a different behavior. > A blank encryption_type field is acting like i expect it from the > plaintext value, but the plaintext value by itself acts different. Please try to be more explicit here. The encryption-type in the authentication storage (sql/ldap) is independent of the authentication mechanisms in the front-ends. For authsql: As long as the encryption_type field correctly describes the encryption of the stored password, the authenticator should be able to correctly validate a provided password. In both cases however, and empty encryption_type field implies plaintext encoding of the stored password. This is however completely unrelated to the AUTH=LOGIN plaintext mechanism in IMAP where the password is passed unencrypted over the wire, but encryption in the database may be very strong. >> Please try it! From reading the code it looks like that for adding a >> user it would end up being plaintext. If modifying a user, the existing >> encoding type is re-used. >> >> >> > > _______________________________________________ > DBmail mailing list > [email protected] > http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail > -- ________________________________________________________________ Paul J Stevens pjstevns @ gmail, twitter, skype, linkedin * Premium Hosting Services and Web Application Consultancy * www.nfg.nl/[email protected]/+31.85.877.99.97 ________________________________________________________________ _______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
