From: | Hannu Krosing <hannu(at)tm(dot)ee> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Vince Vielhaber <vev(at)michvhf(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, The Hermit Hacker <scrappy(at)hub(dot)org>, "Sverre H(dot) Huseby" <sverrehu(at)online(dot)no>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: You're on SecurityFocus.com for the cleartext passwords. |
Date: | 2000-05-06 19:36:21 |
Message-ID: | 39147435.AFF32F7C@tm.ee |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Bruce Momjian wrote:
>
> Now, I we want to move all the stuff to use MD5 rather than the standard
> unix password crypt,
AFAIK, MD5 is one of "the standard password crypt"'s ;)
> that is another option, though I am not sure what
> value it would have.
One advantage would be passwords with more than 8 characters that
matter.
IMO the salt part in the "old" crypt code is there only to make it
harder for people to accidentally discover that other people have
the same password with them, which could easily be avoided by
including the username as kind of supersalt in the md5 string,
so the value passed over wire (and stored in DB would be
MD5('<username>:<passwd>').
If we want to make password hijacking real hard, we could store
the above but ask the client for
MD5(<server-supplied-salt>+MD5(<username>+':'+<passwd>))
and compare that
-------------
Hannu
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-05-06 20:09:04 | Re: You're on SecurityFocus.com for the cleartext passwords. |
Previous Message | Robert B. Easter | 2000-05-06 19:18:35 | Re: You're on SecurityFocus.com for the cleartext passwords. |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-05-06 20:09:04 | Re: You're on SecurityFocus.com for the cleartext passwords. |
Previous Message | Robert B. Easter | 2000-05-06 19:18:35 | Re: You're on SecurityFocus.com for the cleartext passwords. |