Re: scram and \password

From: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: scram and \password
Date: 2017-03-14 10:15:51
Message-ID: e4c3807b-fc53-5657-5372-b156e673a9d5@iki.fi
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 03/14/2017 04:47 AM, Tom Lane wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> I'm not talking about changing the default, just having it be possible
>> to use \password with the new system as it was with the old, whatever
>> exactly we think that means.
>
> Seems to me the intended behavior of \password is to use the best
> available practice. So my guess is that it ought to use SCRAM when
> talking to a >= 10.0 server. What the previous password was ought
> to be irrelevant, even if it could find that out which it shouldn't
> be able to IMO.

If the server isn't set up to do SCRAM authentication, i.e. there are no
"scram" entries in pg_hba.conf, and you set yourself a SCRAM verifier,
you have just locked yourself out of the system. I think that's a
non-starter. There needs to be some more intelligence in the decision.

It would be a lot more sensible, if there was a way to specify in
pg_hba.conf, "scram-or-md5". We punted on that for PostgreSQL 10, but
perhaps we should try to cram that in, after all.

- Heikki

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2017-03-14 10:25:38 Re: [PATCH] SortSupport for macaddr type
Previous Message Amit Kapila 2017-03-14 09:50:04 Re: parallelize queries containing initplans