Re: BUG #10250: pgAdmin III 1.16.1 stores unescaped plaintext password

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
Cc: dlo(at)isam(dot)kiwi, pgsql-bugs(at)postgresql(dot)org, pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: BUG #10250: pgAdmin III 1.16.1 stores unescaped plaintext password
Date: 2014-05-08 00:07:26
Message-ID: 20140508000726.GE2556@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers pgsql-bugs

* Heikki Linnakangas (hlinnakangas(at)vmware(dot)com) wrote:
> (forwarding to pgadmin-hackers)

Ah.

> On 05/07/2014 06:44 PM, Stephen Frost wrote:
> >* dlo(at)isam(dot)kiwi (dlo(at)isam(dot)kiwi) wrote:
> >>but when the credential contains the delimiter (colon) it fails to be
> >>read back out and app responds with "invalid credentials".
> >>
> >>x.x.x.x:5432:*:username:password:with:colons
> >
> >Per the fine documentation, you need to escape any such usage with a
> >backslash. Please review:
>
> Stephen, you missed the context. pgadmin3 saves .pgpass, when you
> check the "store password" checkbox in the connection dialog. And
> apparantly pgadmin3 doesn't do that escaping properly.

Wow, that's pretty rough. Hopefully they'll be able to fix it soon. :)

Thanks,

Stephen

In response to

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Dave Page 2014-05-08 08:07:49 Re: Re: [BUGS] BUG #10250: pgAdmin III 1.16.1 stores unescaped plaintext password
Previous Message Heikki Linnakangas 2014-05-07 20:51:26 Re: [BUGS] BUG #10250: pgAdmin III 1.16.1 stores unescaped plaintext password

Browse pgsql-bugs by date

  From Date Subject
Next Message David Johnston 2014-05-08 00:29:26 Re: Re: BUG #10256: COUNT(*) behaves sort of like RANK() when used over a window containing an ORDER BY
Previous Message Tom Lane 2014-05-08 00:07:17 Re: Re: BUG #10256: COUNT(*) behaves sort of like RANK() when used over a window containing an ORDER BY