Re: Encrypting pg_shadow passwords

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 18:29:09
Message-ID: Pine.BSF.4.30.0106151428110.11597-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:

> Vince Vielhaber <vev(at)michvhf(dot)com> writes:
> >> 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?
>
> > The first three characters are md5 in the code I sent Bruce.
>
> Uh ... so if I use a password that starts with "md5", it breaks?

yup.

> Seems like adding an additional column to pg_shadow would be a better
> technique.

I agree but that was frowned upon for reasons I don't recall now.

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
==========================================================================

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Vince Vielhaber 2001-06-15 18:31:04 Re: Encrypting pg_shadow passwords
Previous Message Tom Lane 2001-06-15 18:27:02 Re: RE: Row Versioning, for jdbc updateable result sets