Search Postgresql Archives

Re: Running untrusted sql safely?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Scott Marlowe wrote:
On Sun, Feb 15, 2009 at 4:39 PM, Christophe <xof@xxxxxxxxxxxx> wrote:
On Feb 15, 2009, at 2:47 PM, Stuart McGraw wrote:

I just hoping for some confirmation that the permissions based approach
did not have some holes in it that I am
not seeing.
Another possibility is to create a set of functions that contain the query
operations you would like to allow, isolate those in a schema, and make that
schema the only thing accessible to the (semi-)trusted users.

I can see that getting complex real fast in a big operation, but for a
database that runs a few big reporting queries every day or sits on an
intranet would be workable.
...

And to actually answer Christophes question: yes, granting only
SELECT to a few tables is enough to prevent them doing anything else
in the database. But watch out for the default permissions on the
public schema of all the databases the users are able to connect to.

Regards
Tino

<<attachment: smime.p7s>>


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux