Re: pgsql: Use GRANT system to manage access to sensitive functions

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Use GRANT system to manage access to sensitive functions
Date: 2016-04-07 01:59:43
Message-ID: CAB7nPqTN1aPjV_yGE=rtBoSNEszeh9__vOwdV7RLtFb0BPZWWA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Thu, Apr 7, 2016 at 10:45 AM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> Use GRANT system to manage access to sensitive functions
>
> Now that pg_dump will properly dump out any ACL changes made to
> functions which exist in pg_catalog, switch to using the GRANT system
> to manage access to those functions.
>
> This means removing 'if (!superuser()) ereport()' checks from the
> functions themselves and then REVOKEing EXECUTE right from 'public' for
> these functions in system_views.sql.

+1.
--
Michael

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2016-04-07 03:00:39 Re: pgsql: Use GRANT system to manage access to sensitive functions
Previous Message Stephen Frost 2016-04-07 01:45:51 pgsql: In pg_dump, split "dump" into "dump" and "dump_contains"

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-04-07 03:00:39 Re: pgsql: Use GRANT system to manage access to sensitive functions
Previous Message Robert Haas 2016-04-07 01:58:50 Re: Move PinBuffer and UnpinBuffer to atomics