Re: [HACKERS] SCRAM in the PG 10 release notes - Mailing list pgsql-hackers

From Jeff Janes
Subject Re: [HACKERS] SCRAM in the PG 10 release notes
Date
Msg-id CAMkU=1y42hMbhj3jZxi8tQsLH1dGwiuo6xc0jKWowxCPmohyhg@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] SCRAM in the PG 10 release notes  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: [HACKERS] SCRAM in the PG 10 release notes
List pgsql-hackers
On Wed, Sep 20, 2017 at 6:42 AM, Peter Eisentraut <peter.eisentraut@2ndquadrant.com> wrote:
On 9/19/17 21:44, Michael Paquier wrote:
>> The patch that Heikki posted seemed reasonable to me as a starting
>> point, but there probably needs to be more "how" information somewhere.
>
> I agree with that.
>
> +   <para>
> +    Installations using MD5 authentication are encouraged to switch to
> +    SCRAM-SHA-256, unless using older client programs or drivers that don't
> +    support it yet.
> +   </para>
> I think that the addition of a link to
> https://wiki.postgresql.org/wiki/List_of_drivers would be appropriate.

I don't have any expectation that that list will be kept up to date.

I am not confident that it will be either, but what could we ever have more confidence in being kept up-to-date than something anyone can update which is hosted on a community asset?  If we can't collectively keep it up-to-date, then shame on us and what hope is there for anything else?  Certainly if it is not linked to from the docs, then it is just that much less likely to be kept up to date.  The problem with it currently is that it implies anything using libpq supports scram, even though a libpq which supports scram has not even been released yet.

Cheers,

Jeff

pgsql-hackers by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: [HACKERS] compress method for spgist - 2
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] compress method for spgist - 2