<p dir="ltr"><br /> On Dec 19, 2014 5:02 PM, "Craig Ringer" <<a
href="mailto:craig@2ndquadrant.com">craig@2ndquadrant.com</a>>wrote:<br /> ><br /> > On 12/19/2014 11:57 PM,
DavePage wrote:<br /> > > Right - we'd have to store the entries somewhere based on the target<br /> > >
serverand the SSH config, and dynamically rebuilt the pgpass file<br /> > > during the connection process. That
seemsa) ugly and b) very fragile.<br /> ><br /> > Darn. I thought libpq had a callback for a password prompt, but
itdoesn't.<br /> ><br /> > Guess we should add that. If libpq gets an auth request from the server<br /> > and
hasno password from the connection string, it should invoke a<br /> > callback (if supplied) that lets the client
supplya password dynamically.<br /> ><p dir="ltr">We definitely should. And we should make sure we design it not to
justsupport passwords but anything we might need to unlock an authentication - say a x509 certificate (doesn't have to
bethe same function, but it should be part of the design considerations for the feature). <p dir="ltr">/Magnus <br />