Re: Possible PostgreSQL 8.3beta4 bug with MD5 authentication in psql?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Dave Page <dpage(at)postgresql(dot)org>
Cc: Mark Cave-Ayland <mark(dot)cave-ayland(at)ilande(dot)co(dot)uk>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Possible PostgreSQL 8.3beta4 bug with MD5 authentication in psql?
Date: 2007-12-07 16:03:40
Message-ID: 20625.1197043420@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dave Page <dpage(at)postgresql(dot)org> writes:
> Just to add a note to that - when running it in the same shell from
> which I started the server with messages going to stdout, it seemed
> clear that it trys to connect once using PGPASSWORD, then when that
> fails, it prompts for the password instead, and then tries to connect
> with that and fails a second time.

Hmmm ... it seems the problem is that we've defined
PQconnectionUsedPassword in such a way that it returns true (causing a
prompt) regardless of whether the reason for the connection failure was
a bad password or not. We might need to reconsider that API.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua D. Drake 2007-12-07 16:08:30 Re: [HACKERS] Uniform policy for author credits in contrib module documentation?
Previous Message Dave Page 2007-12-07 16:00:49 Re: Problem with ControlFileData structure being ABI depe ndent