Re: Why security-definer functions are executable by public by default?

From: hubert depesz lubaczewski <depesz(at)depesz(dot)com>
To: pasman pasmański <pasman(dot)p(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Why security-definer functions are executable by public by default?
Date: 2011-04-06 14:41:43
Message-ID: 20110406144143.GA10011@depesz.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Apr 06, 2011 at 09:06:50AM +0200, pasman pasmański wrote:
> > was pointed to the fact that security definer functions have the same
> > default privileges as normal functions in the same language - i.e. if
> > the language is trusted - public has the right to execute them.
> >
> > maybe i'm missing something important, but given the fact that security
> > definer functions are used to get access to things that you usually
> > don't have access to - shouldn't the privilege be revoked by default,
> > and grants left for dba to decide?
> >
>
> you can create function in schema accesible to dba only.

sure. and I can revoke the privileges and grant the ones I need.

I know I can *fix* it. But I just think that the default should be the
same as with untrusted languages.

depesz

--
The best thing about modern society is how easy it is to avoid contact with it.
http://depesz.com/

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Rob Sargent 2011-04-06 14:53:02 Re: temp tables not dropping at end of script
Previous Message Davenport, Julie 2011-04-06 14:12:55 temp tables not dropping at end of script