Re: BUG #10250: pgAdmin III 1.16.1 stores unescaped plaintext password - Mailing list pgsql-bugs

From Heikki Linnakangas
Subject Re: BUG #10250: pgAdmin III 1.16.1 stores unescaped plaintext password
Date
Msg-id 536A9CCE.9030006@vmware.com
Whole thread Raw
In response to Re: BUG #10250: pgAdmin III 1.16.1 stores unescaped plaintext password  (Stephen Frost <sfrost@snowman.net>)
Responses Re: BUG #10250: pgAdmin III 1.16.1 stores unescaped plaintext password  (Stephen Frost <sfrost@snowman.net>)
List pgsql-bugs
(forwarding to pgadmin-hackers)

On 05/07/2014 06:44 PM, Stephen Frost wrote:
> * dlo@isam.kiwi (dlo@isam.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.

- Heikki


pgsql-bugs by date:

Previous
From: arnaud.mouronval@gmail.com
Date:
Subject: BUG #10256: COUNT(*) behaves sort of like RANK() when used over a window containing an ORDER BY
Next
From: Tom Lane
Date:
Subject: Re: BUG #10256: COUNT(*) behaves sort of like RANK() when used over a window containing an ORDER BY