Date: Mon, 17 May 2021 15:29:04 -0400
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Bruce Momjian <bruce@momjian.us>
Cc: Ian Lawrence Barwick <barwick@gmail.com>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: PG 14 release notes, first draft
Message-ID: <20210517192904.GA4220@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20210517025102.GA24531@momjian.us>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: 
 <https://www.postgresql.org/message-id/20210517192904.GA4220%40alvherre.pgsql>
Precedence: bulk

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@eisentraut.org>
> 	2020-06-10 [c7eab0e97] Change default of password_encryption to scram-sha-256
> 	Author: Peter Eisentraut <peter@eisentraut.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)