Okay, so the problem is, that SASL needs to encrypt the password for its own and because of that i'm forced to store the passwords unencrypted?

Am 03.05.2012 16:24, schrieb Reindl Harald:

Am 03.05.2012 16:22, schrieb cl445:
Has anybody an idea, to get SASL to work with encrypted passwords in the
database?
I used Cyrus SASL and it seems to be impossible
it is technically not possible doing CRAM-MD5 without
acess to the unencrypted passwords - keep in mind that
the different aut mechs are hashing the password in
different ways on client and server






_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

Reply via email to