Re: Re: Proposal for encrypting pg_shadow passwords - Mailing list pgsql-patches

From Vince Vielhaber
Subject Re: Re: Proposal for encrypting pg_shadow passwords
Date
Msg-id Pine.BSF.4.30.0108161516140.14255-100000@paprika.michvhf.com
Whole thread Raw
In response to Re: Re: Proposal for encrypting pg_shadow passwords  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: Re: Proposal for encrypting pg_shadow passwords  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-patches
On Thu, 16 Aug 2001, Bruce Momjian wrote:

> > Peter Eisentraut <peter_e@gmx.net> writes:
> > > I don't follow this argument.  You added a config option that toggles
> > > whether to use the old crypt(3) method or the new md5 method.
> >
> > ?? If the config option works like that, I think it's wrong.  There
> > shouldn't *be* a config option, unless it's one that turns off MD5
> > because the platform hasn't got int64 support.  An MD5-enabled server
> > or client must still be able to do crypt too, in order to speak to
> > older clients or servers.
>
> Sorry, when I said config, I meant pg_hba.conf.  Was that unclear?
>
> Also, I will replace md5.c with pgcrypto/md5.c.

what's the difference?

Vince.
--
==========================================================================
Vince Vielhaber -- KA8CSH    email: vev@michvhf.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
==========================================================================




pgsql-patches by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Re: Proposal for encrypting pg_shadow passwords
Next
From: Fernando Nasser
Date:
Subject: Re: Fix for fetchone() and fetchmany() in Python interface