Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kSx77-0003J9-DS for pgsql-bugs@arkaria.postgresql.org; Thu, 15 Oct 2020 06:51:49 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kSx73-0006gk-O1 for pgsql-bugs@arkaria.postgresql.org; Thu, 15 Oct 2020 06:51:45 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kSrRd-0002Lc-OX for pgsql-bugs@lists.postgresql.org; Thu, 15 Oct 2020 00:48:37 +0000 Received: from mail01.asahi-net.or.jp ([202.224.55.13]) by magus.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kSrRY-0006Q8-Ny for pgsql-bugs@lists.postgresql.org; Thu, 15 Oct 2020 00:48:37 +0000 Received: from client1 (ah203089.dynamic.ppp.asahi-net.or.jp [131.129.203.89]) (Authenticated sender: ZZ5S-AKD) by mail01.asahi-net.or.jp (Postfix) with ESMTPSA id 0FB7312A29C; Thu, 15 Oct 2020 09:48:28 +0900 (JST) From: "akada shigeki" To: "'Tom Lane'" Cc: References: <16672-cdf02792fc851417@postgresql.org> <3640830.1602720588@sss.pgh.pa.us> In-Reply-To: <3640830.1602720588@sss.pgh.pa.us> 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> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 15.0 Thread-Index: AQIe67yghqHCRHRBX/kEIdSmF2V8kQF5pxx4qPt06KA= Content-Language: ja List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk 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 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