| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Vik Fearing <vik(at)postgresfriends(dot)org> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: password_encryption default |
| Date: | 2020-05-25 09:45:25 |
| Message-ID: | bb859650-4117-b002-46b8-57b35881a459@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-05-22 23:23, Jonathan S. Katz wrote:
>> Yeah. But there's still something to Jonathan's argument, because 9.6
>> will go EOL in November 2021, which is pretty close to when v14 will
>> reach public release (assuming we can hold to the typical schedule).
>> If we do it in v13, there'll be a full year where still-supported
>> versions of PG can't do SCRAM, implying that clients would likely
>> fail to connect to an up-to-date server.
>
> ^ that's what I meant.
Here is a proposed patch for PG14 then.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Change-default-of-password_encryption-to-scram-sha-2.patch | text/plain | 4.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2020-05-25 09:55:10 | Re: some grammar refactoring |
| Previous Message | Michael Paquier | 2020-05-25 09:29:10 | Re: segmentation fault using currtid and partitioned tables |