pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: akada shigeki <zz5s-akd@asahi-net.or.jp>
To: 'Tom Lane' <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@lists.postgresql.org
Subject: RE: BUG #16672: Postgres user passwords are corrupted during migration
Date: Thu, 15 Oct 2020 09:48:26 +0900
Message-ID: <000101d6a28c$e4fdfca0$aef9f5e0$@asahi-net.or.jp> (raw)
In-Reply-To: <3640830.1602720588@sss.pgh.pa.us>
References: <16672-cdf02792fc851417@postgresql.org>
	<3640830.1602720588@sss.pgh.pa.us>

Mr.Tom Lane
solved.
I was able to restore by changing SCRAM-SHA-256 in HBA.Conf to MD5.
Does this mean that PSQL doesn't support SHA-256 encryption?

-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us] 
Sent: Thursday, October 15, 2020 9:10 AM
To: zz5s-akd@asahi-net.or.jp
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16672: Postgres user passwords are corrupted during
migration

PG Bug reporting form <noreply@postgresql.org> writes:
> The postgres user password is corrupted when migrating from Postgresql 
> 12.4 to Postgresql 13.

I tried to verify that claim, without success: AFAICS, dump/reload will
correctly propagate the password to the new server, in either md5 or SCRAM
format.

You have not shown very much supporting detail, but I wonder whether the
password is hashed in md5 format and the v13 server's pg_hba.conf is set to
only allow SCRAM passwords.  The report sent to the client intentionally
just says "password authentication failed", but you could look in the
postmaster log to see what it says about the failure.
Also, look in pg_authid (of either server), or in the dump file, to see
whether the rolpassword value starts with "md5" or "SCRAM-SHA-256".

			regards, tom lane






view thread (5+ messages)  latest in thread

Message-ID: <000101d6a28c$e4fdfca0$aef9f5e0$@asahi-net.or.jp>
Permalink:  ../000101d6a28c$e4fdfca0$aef9f5e0$@asahi-net.or.jp/
Also on:    postgresql.org/message-id/000101d6a28c$e4fdfca0$aef9f5e0$@asahi-net.or.jp

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: zz5s-akd@asahi-net.or.jp, tgl@sss.pgh.pa.us, pgsql-bugs@lists.postgresql.org
  Subject: RE: BUG #16672: Postgres user passwords are corrupted during migration
  In-Reply-To: <000101d6a28c$e4fdfca0$aef9f5e0$@asahi-net.or.jp>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox