Re: Add on_trusted_init and on_untrusted_init to plperl UPDATED [PATCH]
От | Alex Hunsaker |
---|---|
Тема | Re: Add on_trusted_init and on_untrusted_init to plperl UPDATED [PATCH] |
Дата | |
Msg-id | 34d269d41002031049q1ab33a61v4f13a67b8c25009b@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Add on_trusted_init and on_untrusted_init to plperl UPDATED [PATCH] (Alex Hunsaker <badalex@gmail.com>) |
Ответы |
Re: Add on_trusted_init and on_untrusted_init to plperl
UPDATED [PATCH]
|
Список | pgsql-hackers |
On Wed, Feb 3, 2010 at 11:43, Alex Hunsaker <badalex@gmail.com> wrote: > On Wed, Feb 3, 2010 at 11:28, Tom Lane <tgl@sss.pgh.pa.us> wrote: >> Tim Bunce <Tim.Bunce@pobox.com> writes: >>> I do see a need for a GRANT check and I'm adding one now (based on >>> the code in CreateFunction() in functioncmds.c - thanks to RhodiumToad >>> on IRC for the pointer). >> >> What exactly are you proposing to check, and where, and what do you >> think that will fix? > > Non plperl ... Put another way: HEAD: only people with plperl granted can make functions to manipulate $_SHARED PATCH: anyone can set plperl.plperl_safe_init (but note not plperlu_init as its SUSER) and manipulate $_SHARED Proposed fix: only people with plperl granted can set plperl.plplerl_safe_init and hence restore HEAD behavior
В списке pgsql-hackers по дате отправления: