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

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Álvaro Hernández Tortosa <aht(at)8kdata(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Subject: Re: Letting the client choose the protocol to use during a SASL exchange
Date: 2017-04-06 22:33:36
Message-ID: CAB7nPqQqfE0C-VDdZ6Ch1e33UtA1hsiw1aVeOCtdAgBrXwMPNw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Apr 7, 2017 at 7:29 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On 6 April 2017 at 16:15, Álvaro Hernández Tortosa <aht(at)8kdata(dot)com> wrote:
>
>> Per the SCRAM RFC, it is the server who advertises and the client who picks.
>
> Yes, but what does the RFC say about how to handle servers with an pg_hba.conf?
>
> How and what will we advertise?

Did you read the first email of this thread? The RFC says that the
protocol implementers are free to do what they want as this is
protocol-specific. At least that's what I understand.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2017-04-06 22:35:06 Re: Time to change pg_regress diffs to unified by default?
Previous Message Andres Freund 2017-04-06 22:31:03 Time to change pg_regress diffs to unified by default?