From: | Hannu Krosing <hannu(at)tm(dot)ee> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Vince Vielhaber <vev(at)michvhf(dot)com>, 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-07 07:11:21 |
Message-ID: | 39151719.9BD2DB3A@tm.ee |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Bruce Momjian wrote:
>
> Another idea is to add code to 7.1 to convert non-md5 shadow password
> fields to md5 format. Since we already have special handling to do
> pg_pwd, we could do it there. Seems like a plan. MD5 format is all
> hex digits of a specific length. No way to get that confused with a
> real password.
One way to approach it in a semi-transparent way would be to add a
column md5passwd to pg_shadow and set up a trigger to automatically
update it whenever passwd is inserted/updated (and for
security-concious people the same trigger would empty the passwd
field itself, or set it to some special value that disables
crypt/cleartext logins)
the WITH ENCRYPTED PASSWORD would then update md5passwd directly, and
reset the passwd field.
I still think that the easiest way to get unique hashes would be to use
the username as salt when generating the value for md5passwd .
----------------
Hannu
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2000-05-07 07:21:56 | Re: So we're in agreement.... |
Previous Message | Vince Vielhaber | 2000-05-07 06:41:10 | Re: So we're in agreement.... |
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2000-05-07 07:21:56 | Re: So we're in agreement.... |
Previous Message | Vince Vielhaber | 2000-05-07 06:41:10 | Re: So we're in agreement.... |