Re: Massively annoying bug still not fixed in v1.20 :-(

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Craig Ringer <craig(at)2ndquadrant(dot)com>
Cc: hushthatbush(at)hushmail(dot)com, pgadmin-support(at)postgresql(dot)org, Dave Page <dpage(at)pgadmin(dot)org>
Subject: Re: Massively annoying bug still not fixed in v1.20 :-(
Date: 2014-12-19 16:08:35
Message-ID: CABUevEy-+_F3DYR-harXy0vkiOeO4yirxsuj56NQ-+jqmbiv4g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

On Dec 19, 2014 5: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.
>

We definitely should. And we should make sure we design it not to just
support passwords but anything we might need to unlock an authentication -
say a x509 certificate (doesn't have to be the same function, but it should
be part of the design considerations for the feature).

/Magnus

In response to

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Melvin Davidson 2014-12-20 17:50:37 PgAdmin III 1.20 windows - not valid
Previous Message Dave Page 2014-12-19 16:06:28 Re: Massively annoying bug still not fixed in v1.20 :-(