Re: add a MAC check for TRUNCATE
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Yuli Khodorkovskiy <yuli.khodorkovskiy@crunchydata.com>
Cc: Stephen Frost <sfrost@snowman.net>, Kohei KaiGai <kaigai@heterodb.com>,
pgsql-hackers@lists.postgresql.org
Date: 2019-09-06T15:47:35Z
Lists: pgsql-hackers
Yuli Khodorkovskiy <yuli.khodorkovskiy@crunchydata.com> writes:
> Ah, now I remember why I didn't add regressions to the original patch.
> As stated at the top of the thread, the "db_table: { truncate }"
> permission does not currently exist in refpolicy. A workaround would
> be to add the policy with CIL, but that adds unneeded complexity to
> the regressions. I think the correct path forward is:
> 1) Get the sepgsql changes in without policy/regressions
> 2) Send a patch to refpolicy for the new permission
> 3) Once Redhat updates the selinux-policy-targeted RPM to include the
> new permissions, I will send an update to the sepgsql regressions and
> policy.
That's going to be a problem. I do not think it will be acceptable
to commit tests that fail on less-than-bleeding-edge SELinux.
regards, tom lane
Commits
-
Update sepgsql to add mandatory access control for TRUNCATE
- 4f66c93f6143 13.0 landed
-
Add object TRUNCATE hook
- f7a2002e82cf 13.0 landed
-
postgres_fdw: Fix error message for PREPARE TRANSACTION.
- 879c11761571 13.0 cited