Re: BUG #16672: Postgres user passwords are corrupted during migration

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "akada shigeki" <zz5s-akd(at)asahi-net(dot)or(dot)jp>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #16672: Postgres user passwords are corrupted during migration
Date: 2020-10-15 01:07:31
Message-ID: 3643196.1602724051@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"akada shigeki" <zz5s-akd(at)asahi-net(dot)or(dot)jp> writes:
> 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?

No, it means if you want to use SCRAM authentication then you need the
password that's stored in pg_authid to be hashed with SCRAM. The password
you carried forward from v12 evidently isn't. (Again, look into pg_authid
to confirm that.)

Do this, in either v12 or v13, to update the password:

set password_encryption to "scram-sha-256";
alter user postgres with password 'clear text password here';

The system cannot do this for you because there's no way to recover
the cleartext password from the md5 hash.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Thomas Munro 2020-10-15 01:26:36 Re: BUG #16663: DROP INDEX did not free up disk space: idle connection hold file marked as deleted
Previous Message akada shigeki 2020-10-15 00:48:26 RE: BUG #16672: Postgres user passwords are corrupted during migration