Re: Letting the client choose the protocol to use during a SASL exchange

From: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
To: Craig Ringer <craig(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Letting the client choose the protocol to use during a SASL exchange
Date: 2017-04-07 09:08:44
Message-ID: afbfada1-56c7-30ac-691e-ca7a5d42aa32@iki.fi
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 04/07/2017 11:57 AM, Craig Ringer wrote:
> On 7 April 2017 at 16:33, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:
>
>> That list of supported authentication methods would need to be included in
>> the startup message. Unfortunately, there is no way to add options to the
>> startup message, without breaking compatibility with old servers. If there
>> is an option in the startup message that the server doesn't understand, it
>> will treat it as a GUC, and you get an "unrecognized configuration
>> parameter" after authentication.
>
> sasl.mechanisms = 'SCRAM_SHA256'
>
> :p
>
> No, I'm not seriously suggesting we abuse that.

Hmm, that's not such a bad idea, actually. It only goes back to 9.2,
though. Before that, the prefix needed to be listed in
custom_variable_classes, or you got an error. 9.2 is the oldest
supported version, but libpq should still be able to connect to older
versions.

- Heikki

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fabien COELHO 2017-04-07 09:43:53 Re: pgbench - allow to store select results into variables
Previous Message Mithun Cy 2017-04-07 09:07:23 Re: Proposal : For Auto-Prewarm.