Re: Re: Proposal for encrypting pg_shadow passwords

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Vince Vielhaber <vev(at)michvhf(dot)com>
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 21:46:55
Message-ID: 200108162146.f7GLkui25149@candle.pha.pa.us
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?

People say the current md5.c assumes 64bit integers.

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

Browse pgsql-patches by date

  From Date Subject
Next Message Barry Lind 2001-08-17 02:21:01 Re: Re: [JDBC] JDBC pg_description update needed for CVS tip
Previous Message Bruce Momjian 2001-08-16 21:45:23 Re: [PATCHES] Re: JDBC pg_description update needed for CVS tip