From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Ian Lawrence Barwick <barwick(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PG 14 release notes, first draft |
Date: | 2021-05-17 19:29:04 |
Message-ID: | 20210517192904.GA4220@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2021-May-16, Bruce Momjian wrote:
> OK, what I was trying to say was that if you dump/restore, and the old
> password was md5, the newly-restored password will be md5, but it was
> very unclear. I changed it to this:
>
> <listitem>
> <!--
> Author: Peter Eisentraut <peter(at)eisentraut(dot)org>
> 2020-06-10 [c7eab0e97] Change default of password_encryption to scram-sha-256
> Author: Peter Eisentraut <peter(at)eisentraut(dot)org>
> 2020-06-10 [c7eab0e97] Change default of password_encryption to scram-sha-256
> -->
>
> <para>
> Change the default of the password_encryption server parameter to
> scram-sha-256 (Peter Eisentraut)
> </para>
>
> <para>
> Previously it was md5. All new passwords will be stored as SHA256
> unless this server variable is changed or the password is specified
> in md5 format. Also, the legacy (and undocumented) boolean-like
> values which were previously synonyms for <literal>md5</literal>
> are no longer accepted.
> </para>
> </listitem>
Ah, yeah, now I understand. WFM.
Thanks
--
Álvaro Herrera 39°49'30"S 73°17'W
"La fuerza no está en los medios físicos
sino que reside en una voluntad indomable" (Gandhi)
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2021-05-17 19:45:44 | Re: PG 14 release notes, first draft |
Previous Message | Andres Freund | 2021-05-17 18:56:46 | Re: prion failed with ERROR: missing chunk number 0 for toast value 14334 in pg_toast_2619 |