From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
Cc: | hushthatbush(at)hushmail(dot)com, "pgadmin-support(at)postgresql(dot)org" <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: Massively annoying bug still not fixed in v1.20 :-( |
Date: | 2014-12-19 16:06:28 |
Message-ID: | CA+OCxozeiRg1hHhDbUvug4sH_63JZYLPDrzzi56LRR35yVDagg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
On Fri, Dec 19, 2014 at 4:02 PM, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:
> On 12/19/2014 11:57 PM, Dave Page wrote:
>> Right - we'd have to store the entries somewhere based on the target
>> server and the SSH config, and dynamically rebuilt the pgpass file
>> during the connection process. That seems a) ugly and b) very fragile.
>
> Darn. I thought libpq had a callback for a password prompt, but it doesn't.
>
> Guess we should add that. If libpq gets an auth request from the server
> and has no password from the connection string, it should invoke a
> callback (if supplied) that lets the client supply a password dynamically.
That would be very handy.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2014-12-19 16:08:35 | Re: Massively annoying bug still not fixed in v1.20 :-( |
Previous Message | Craig Ringer | 2014-12-19 16:02:27 | Re: Massively annoying bug still not fixed in v1.20 :-( |