Re: md5 password valid and invalid after upgrading

From: Kyle MacMillan <macattackftw(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: md5 password valid and invalid after upgrading
Date: 2023-09-28 21:49:39
Message-ID: CACW=iPtLgDLcLDkTxCfwmkFcMQF4OVn05kGZKJeR55QrOfmc_A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi Tom,

The server was AWS's "serverless" Aurora service, I'm not sure where logs
for that would be found. I did not see any error logs generated.

I found a solution, but I still think the docs do not illustrate the
regression, at the very least. To resolve this issue I had to paste my
existing password into the master password of the server. I was able to
connect to the database after that "change".

No configuration changes, just re-inputting my existing password into the
server, then I was able to remotely connect with psql 14.

Kyle

On Wed, Sep 27, 2023 at 6:25 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Kyle MacMillan <macattackftw(at)gmail(dot)com> writes:
> > Here's the connection method:
> > psql -h <url> -d <database>
>
> > I'm then prompted for a password and enter the password.
>
> > And the error:
> > psql: error: connection to server at <redacted> failed: fe_sendauth:
> error
> > sending password authentication
>
> What appears in the server's log when you do this?
>
> regards, tom lane
>

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2023-09-28 21:53:41 Re: Broken type checking for empty subqueries
Previous Message David Rowley 2023-09-28 21:10:33 Re: Broken type checking for empty subqueries