* Florian Pflug ([EMAIL PROTECTED]) wrote:
> Stephen Frost wrote:
> >Uh, have the admin create appropriate views.
> I meant letting them use it to connect to abitrary databases and hosts, not
> executing only predefined quries. My wording wasn't clear in that regard,
> though.

Perhaps I wasn't clear.  My response to that is "don't.".  It's not a
safe or sane thing for a user to be able to do.

> >I disagree.  What dblink *does* is insecure and in general *shouldn't*
> >be something regular users can do.  That goes well and beyond just the
> >ident case, imv, but it's handy thing to point to atm.

> I fail to see why dblink is any more insecure than, say, plpgsql or
> plperl (not plperlu). It doesn't give any more priviliges than pgsql
> would. The only exception IMHO are privileges that you get because
> dblink issues that connection from a specific machine as a specific user.

Trusted languages shouldn't be able to open socket connections.  If
plpgsql (erm, don't think so) or plperl (I hope it can't...) can do that
then they should be marked as untrusted.



Attachment: signature.asc
Description: Digital signature

Reply via email to