From: | Vince Vielhaber <vev(at)michvhf(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Encrypting pg_shadow passwords |
Date: | 2001-06-15 15:28:15 |
Message-ID: | Pine.BSF.4.30.0106151121580.9395-100000@paprika.michvhf.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, 15 Jun 2001, Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > I think the script idea may be best but it will have to be saved
> > somewhere so once you run it all future password changes are encrypted
> > in pg_shadow.
>
> More to the point, how does the postmaster know that it's now dealing
> with encrypted passwords and must use the double-salt auth method?
> Seems to me that this is not a simple matter of changing the data in one
> column of pg_shadow.
The first three characters are md5 in the code I sent Bruce. The
auth stuff starts looking at the 4th character of the password column
in pg_shadow.
Vince.
--
==========================================================================
Vince Vielhaber -- KA8CSH email: vev(at)michvhf(dot)com http://www.pop4.net
56K Nationwide Dialup from $16.00/mo at Pop4 Networking
Online Campground Directory http://www.camping-usa.com
Online Giftshop Superstore http://www.cloudninegifts.com
==========================================================================
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Meskes | 2001-06-15 15:28:54 | Re: NOTICE messages |
Previous Message | Vince Vielhaber | 2001-06-15 15:00:17 | Re: Encrypting pg_shadow passwords |