From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | Kyle MacMillan <macattackftw(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: md5 password valid and invalid after upgrading |
Date: | 2023-09-27 08:04:24 |
Message-ID: | 01fbb3d2f280a7691ae6e563870c00d19fadb02e.camel@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Tue, 2023-09-26 at 19:14 -0400, Kyle MacMillan wrote:
> Issue:
> Unable to log into database with md5 password, only after upgrading remote system's psql version.
>
> Error:
> psql: error: connection to server at... failed: fe_sendauth: error sending password authentication
>
> Steps:
> 1. Setup Postgres 11.17 with an MD5 password
> 2. Access the DB from a remote system that only has psql 9.6
> 3. Upgrade DB to Postgres15.x
> 4. Log into database using psql 9.6 and the original password
> 5. Observe no issues
> 6. Upgrade psql on remote system to 14.x
> 7. Attempt to log in and see an error
> The documentation regarding Postgres 14 does not specify the old password will not work.
> It specifies the default was changed and that new passwords will be stored as SHA256.
> I am not using boolean-like values for my current password.
>
> psql14 does not appear to recognize that it needs to use md5 but psql9 doesn't know any better, so it works.
Are you sure that there is no additional error message like "out of memory"
or "could not encrypt password"? Was step 4 executed on the remote system
that was later upgraded (so that we can rule out network problems etc.)?
Is SSL enabled on the server?
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | Sorin Mircioiu | 2023-09-27 08:32:45 | Re: PostgreSQL's processes blocking each other are not detected as deadlock |
Previous Message | Dean Rasheed | 2023-09-27 07:29:27 | Re: BUG #18103: bugs of concurrent merge into when use different join plan |