| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Dave Page <dpage(at)pgadmin(dot)org> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: More sepgsql weirdness |
| Date: | 2021-04-13 17:21:57 |
| Message-ID: | CA+TgmoayH=8YQNTjomuTg1Qd_n8JZ8-2GPHb5rdHDCFerLTJPw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Apr 13, 2021 at 10:33 AM Dave Page <dpage(at)pgadmin(dot)org> wrote:
> On a system with selinux and sepgsql configured, search path resolution appears to fail if sepgsql is in enforcing mode, but selinux is in permissive mode (which, as I understand it, should cause sepgsql to behave as if it's in permissive mode anyway - and does for other operations). Regardless of whether my understanding of the interaction of the two permissive modes is correct, I don't believe the following should happen:
I agree that this sounds like something which shouldn't happen if the
system is in permissive mode, but I think the behavior itself is
deliberate. See OAT_NAMESPACE_SEARCH and commit
e965e6344cfaff0708a032721b56f61eea777bc5.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Charlie Hornsby | 2021-04-13 17:28:50 | Re: pg_upgrade check for invalid role-specific default config |
| Previous Message | Nandni Mehla | 2021-04-13 16:31:13 | Proposal for working open source with PostgreSQL |