Re: [HACKERS] unprivileged contrib and pl install
От | Jeremy Drake |
---|---|
Тема | Re: [HACKERS] unprivileged contrib and pl install |
Дата | |
Msg-id | Pine.BSO.4.64.0701251521480.23712@resin.csoft.net обсуждение исходный текст |
Ответ на | Re: [HACKERS] unprivileged contrib and pl install (Jeremy Drake <pgsql@jdrake.com>) |
Список | pgsql-patches |
On Wed, 24 Jan 2007, Jeremy Drake wrote: > On Wed, 24 Jan 2007, Tom Lane wrote: > > > In detail, it'd look something like: > > > > * For an untrusted language: must be superuser to either create or use > > the language (no change from current rules). Ownership of the > > pg_language entry is really irrelevant, as is its ACL. > > > > * For a trusted language: > > > > * if pg_pltemplate.something is ON: either a superuser or the current > > DB's owner can CREATE the language. In either case the pg_language > > entry will be marked as owned by the DB owner (pg_database.datdba), > > which means that subsequently he (or a superuser) can grant or deny > > USAGE within his DB. > > > > * if pg_pltemplate.something is OFF: must be superuser to CREATE the > > language; subsequently it will be owned by you, so only you or another > > superuser can grant or deny USAGE (same behavior as currently). > > I think I have what is described here implemented in this patch, so that > it can be better understood. Thoughts? This version of the patch creates a shared dependency on the language owner. I have thought of some other questions about the owner stuff which I will send on -hackers... -- Afternoon, n.: That part of the day we spend worrying about how we wasted the morning.
Вложения
В списке pgsql-patches по дате отправления: