Thank you Gal and Tzafrir.
I think I'll drop support for CRAM-MD5 and DIGEST-MD5 for now.
--
Oded
::..
OMG what is the teddy bear doing to that little boy!
=
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscr
On Sunday 14 September 2003 16:23, Oded Arbel wrote:
> As I understand, this is only required so that the authentication agent (be
it
> sasl, pam or whatever) can encode the password in MD5. is it possible to
> store the password on the server already encoded in MD5 ? that would be the
> best
On Sun, Sep 14, 2003 at 04:23:09PM +0300, Oded Arbel wrote:
> On Sunday 14 September 2003 15:47, Gal Goldschmidt wrote:
> > Hi,
> >
> > Both DIGEST-MD5 and CRAM-MD5 require the password to be stored on the
> > server in clear text(!).
>
> As I understand, this is only required so that the authent
On Sunday 14 September 2003 15:47, Gal Goldschmidt wrote:
> Hi,
>
> Both DIGEST-MD5 and CRAM-MD5 require the password to be stored on the
> server in clear text(!).
As I understand, this is only required so that the authentication agent (be it
sasl, pam or whatever) can encode the password in MD
Hi,
Both DIGEST-MD5 and CRAM-MD5 require the password to be stored on the server
in clear text(!). The password is used as the key for authentication.
On one side you have plain and login with encrypted store on the server but
the password is sent unencrypted over the network and then you have
Hi list.
I'm setting up a mail server with all the bells and whistles, and I'm trying
including support for authentication using DIGEST-MD5 and CRAM-MD5.
I've setup postfix to auth using SASL2, and SASL to use PAM and PAM to use
MySQL (long winded - I could use some hints on how to shorten thi
