Re: [HACKERS] pg_ls_dir & friends still have a hard-coded superuser check

Поиск
Список
Период
Сортировка
От Greg Stark
Тема Re: [HACKERS] pg_ls_dir & friends still have a hard-coded superuser check
Дата
Msg-id CAM-w4HOQfcHvoZ0a7uh3ERuV25cjZJV9pT+qf--Q8TzEh6h=TA@mail.gmail.com
обсуждение исходный текст
Ответ на [HACKERS] pg_ls_dir & friends still have a hard-coded superuser check  (Robert Haas <robertmhaas@gmail.com>)
Ответы Re: [HACKERS] pg_ls_dir & friends still have a hard-coded superuser check  (Robert Haas <robertmhaas@gmail.com>)
Re: [HACKERS] pg_ls_dir & friends still have a hard-coded superuser check  (Stephen Frost <sfrost@snowman.net>)
Список pgsql-hackers
I tend to agree. But in the past when this came up people pointed out
you could equally do things this way and still grant all the access
you wanted using SECURITY DEFINER. Arguably that's a better approach
because then instead of auditing the entire monitor script you only
need to audit this one wrapper function, pg_ls_monitor_dir() which
just calls pg_ls_dir() on this one directory.



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Antonin Houska
Дата:
Сообщение: Re: [HACKERS] PoC: Grouped base relation
Следующее
От: David Fetter
Дата:
Сообщение: Re: [HACKERS] COPY as a set returning function