Re: dblink connection security - Mailing list pgsql-patches

From Gregory Stark
Subject Re: dblink connection security
Date
Msg-id 87abugeztk.fsf@oxford.xeocode.com
Whole thread Raw
In response to Re: dblink connection security  (Robert Treat <xzilla@users.sourceforge.net>)
List pgsql-patches
"Robert Treat" <xzilla@users.sourceforge.net> writes:

>>  In particular Postgres's "trust" authentication is one such system. It
>>  authenticates connecting users based on the unix userid of the process
>>  forming the connection. In typical configurations any user who is granted
>>  execute access to dblink can form connections as the "postgres" user which
>>  is the database super-user. If "trust" authentication is disabled this is
>>  no longer an issue.
>
> Did you mean s/trust/ident/g, otherwise I don't think I understand the
> above...   granted the combination of trust for localhost does open a door
> for remote users if they have access to dblink, but I don't think that's what
> you were trying to say.

Er quite right. Moreover it's not even true that ``"if "ident" authentication
is disabled this is no longer an issue''. It's still possible to have other
restrictions in pg_hba which dblink would allow you to circumvent. That
sentence is too generous of a promise.

--
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com


pgsql-patches by date:

Previous
From: "Chuck McDevitt"
Date:
Subject: Re: SPI-header-files safe for C++-compiler
Next
From: Stephen Frost
Date:
Subject: Re: dblink connection security