Re: Encrypting pg_shadow passwords - Mailing list pgsql-hackers

From Vince Vielhaber
Subject Re: Encrypting pg_shadow passwords
Date
Msg-id Pine.BSF.4.30.0106151121580.9395-100000@paprika.michvhf.com
Whole thread Raw
In response to Re: Encrypting pg_shadow passwords  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Encrypting pg_shadow passwords  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, 15 Jun 2001, Tom Lane wrote:

> Bruce Momjian <pgman@candle.pha.pa.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@michvhf.com    http://www.pop4.net        56K Nationwide Dialup from $16.00/mo
atPop4 Networking       Online Campground Directory    http://www.camping-usa.com      Online Giftshop Superstore
http://www.cloudninegifts.com
==========================================================================





pgsql-hackers by date:

Previous
From: "Dave Cramer"
Date:
Subject: Re: RE: Row Versioning, for jdbc updateable result sets
Next
From: Doug McNaught
Date:
Subject: Re: UNIQUE INDEX unaware of transactions