From: | Vince Vielhaber <vev(at)michvhf(dot)com> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: Re: Proposal for encrypting pg_shadow passwords |
Date: | 2001-08-16 19:16:39 |
Message-ID: | Pine.BSF.4.30.0108161516140.14255-100000@paprika.michvhf.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
On Thu, 16 Aug 2001, Bruce Momjian wrote:
> > Peter Eisentraut <peter_e(at)gmx(dot)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(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 | Fernando Nasser | 2001-08-16 20:59:17 | Re: Fix for fetchone() and fetchmany() in Python interface |
Previous Message | Bruce Momjian | 2001-08-16 18:08:43 | Re: Re: Proposal for encrypting pg_shadow passwords |