Re: Encrypting pg_shadow passwords

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Jim Mercer <jim(at)reptiles(dot)org>
Cc: Lincoln Yeoh <lyeoh(at)pop(dot)jaring(dot)my>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Encrypting pg_shadow passwords
Date: 2001-06-26 15:03:38
Message-ID: 200106261503.f5QF3cT06893@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On Mon, Jun 25, 2001 at 02:34:51PM +0800, Lincoln Yeoh wrote:
> > At 12:51 AM 26-06-2001 -0400, Jim Mercer wrote:
> > >this is not so much an enhancement, but a correction of what i think the
> > >original "password" authentication scheme was supposed to allow.
> >
> > Yep it's a correction. pg_shadow shouldn't have been in plaintext in the
> > first place.
> >
> > host all 127.0.0.1 255.255.255.255 password
> > should have meant check crypted passwords in pg_shadow.
> >
> > Given your suggestion, what happens when someone does an ALTER USER ...
> > WITH PASSWORD ....?
> >
> > Might it be too late to do a fix?
>
> i didn't want to change things too much. in the case of ALTER USER, the
> code would need to encrypt the password beforehand, either inline, or
> using a pgsql-contrib crypt() function. (i have this if you want it)
>
> the fix is for the authentication behaviour, not the adminitrative interface
> (ie. ALTER USER).

But the fix disables crypt authentication, at least until we do double
encryption.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2001-06-26 15:05:55 Re: Re: Encrypting pg_shadow passwords
Previous Message Bruce Momjian 2001-06-26 15:02:15 Re: Encrypting pg_shadow passwords