Re: Possibility to disable `ALTER SYSTEM`
От | Tom Lane |
---|---|
Тема | Re: Possibility to disable `ALTER SYSTEM` |
Дата | |
Msg-id | 2391022.1706675128@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Possibility to disable `ALTER SYSTEM` (Magnus Hagander <magnus@hagander.net>) |
Ответы |
Re: Possibility to disable `ALTER SYSTEM`
|
Список | pgsql-hackers |
Magnus Hagander <magnus@hagander.net> writes: > On Tue, Jan 30, 2024 at 10:48 PM Tom Lane <tgl@sss.pgh.pa.us> wrote: >> I was imagining using selinux and/or sepgsql to directly prevent >> writing postgresql.auto.conf from the Postgres account. > Wouldn't a simple "chattr +i postgresql.auto.conf" work? Hmm, I'm not too familiar with that file attribute, but it looks like it'd work (on platforms that support it). My larger point here is that trying to enforce restrictions on superusers *within* Postgres is simply not a good plan, for largely the same reasons that Robert questioned making the GUC mechanism police itself. It needs to be done outside, either at the filesystem level or via some other kernel-level security system. regards, tom lane
В списке pgsql-hackers по дате отправления: