| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | Dave Page <dpage(at)pgadmin(dot)org> |
| 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:02:27 |
| Message-ID: | 54944C13.8000800@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
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.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2014-12-19 16:06:28 | Re: Massively annoying bug still not fixed in v1.20 :-( |
| Previous Message | Dave Page | 2014-12-19 15:57:16 | Re: Massively annoying bug still not fixed in v1.20 :-( |