Re: dblink vs SQL/MED - security and implementation details - Mailing list pgsql-hackers

From Tom Lane
Subject Re: dblink vs SQL/MED - security and implementation details
Date
Msg-id 11748.1231278058@sss.pgh.pa.us
Whole thread Raw
In response to Re: dblink vs SQL/MED - security and implementation details  (Martin Pihlak <martin.pihlak@gmail.com>)
List pgsql-hackers
Martin Pihlak <martin.pihlak@gmail.com> writes:
> Usually it would have been the server owner who created those user
> mappings in the first place -- so the passwords are already known
> to him/her. Of course it is possible to create the mappings first
> and later change the ownership of the server, thus exposing the
> passwords to a new role. But IMHO, it would be reasonable to assume
> that the owner of the server has full control over its user mappings.

So the DBA should know his users' passwords for remote sites?  That's
not normally considered good security practice.

If the passwords were encrypted strings it might be acceptable, but
without some libpq changes I think they'd have to be cleartext :-(
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: parallel restore
Next
From: Martijn van Oosterhout
Date:
Subject: Re: [GENERAL] ERROR: failed to find conversion function from "unknown" to text