Re: Re: Proposal for encrypting pg_shadow passwords

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: 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 14:20:20
Message-ID: 9639.997971620@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> We aren't. I can do that, but have not discussed it yet. If we do it
> is clearly a protocol change. How will old clients handle longer salt,
> and how do I know if they are older if I don't bump up the protocol
> version number?

All of this is under the aegis of a new auth method code, so it doesn't
matter. Either clients handle the new auth method, or they don't.

The problem with bumping the protocol version number is that it breaks
client-to-server compatibility *whether or not a particular connection
needs the new auth method*. Eg, a new client will be unable to talk to
an old server. This is not good.

regards, tom lane

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2001-08-16 14:33:42 Re: Re: Proposal for encrypting pg_shadow passwords
Previous Message Bruce Momjian 2001-08-16 14:08:43 Re: Re: Proposal for encrypting pg_shadow passwords