4 Commits (9919f4fef1df2edf40e1a2a2971f97ff2d23cc3c)

Author	SHA1	Message	Date
Joe Conway	1c419abffb	Fix sepgsql regression tests. ... The regression tests for sepgsql were broken by changes in the base distro as-shipped policies. Specifically, definition of unconfined_t in the system default policy was changed to bypass multi-category rules, which the regression test depended on. Fix that by defining a custom privileged domain (sepgsql_regtest_superuser_t) and using it instead of system's unconfined_t domain. The new sepgsql_regtest_superuser_t domain performs almost like the current unconfined_t, but restricted by multi-category policy as the traditional unconfined_t was. The custom policy module is a self defined domain, and so should not be affected by related future system policy changes. However, it still uses the unconfined_u:unconfined_r pair for selinux-user and role. Those definitions have not been changed for several years and seem less risky to rely on than the unconfined_t domain. Additionally, if we define custom user/role, they would need to be manually defined at the operating system level, adding more complexity to an already non-standard and complex regression test. Back-patch to 9.3. The regression tests will need more work before working correctly on 9.2. Starting with 9.2, sepgsql has had dependencies on libselinux versions that are only available on newer distros with the changed set of policies (e.g. RHEL 7.x). On 9.1 sepgsql works fine with the older distros with original policy set (e.g. RHEL 6.x), and on which the existing regression tests work fine. We might want eventually change 9.1 sepgsql regression tests to be more independent from the underlying OS policies, however more work will be needed to make that happen and it is not clear that it is worth the effort. Kohei KaiGai with review by Adam Brightwell and me, commentary by Stephen, Alvaro, Tom, Robert, and others.	11 years ago
Robert Haas	1cea9bbb21	sepgsql: Support for new post-ALTER access hook. ... KaiGai Kohei	13 years ago
Alvaro Herrera	f4c4335a4a	Add context info to OAT_POST_CREATE security hook ... ... and have sepgsql use it to determine whether to check permissions during certain operations. Indexes that are being created as a result of REINDEX, for instance, do not need to have their permissions checked; they were already checked when the index was created. Author: KaiGai Kohei, slightly revised by me	13 years ago
Robert Haas	e914a144d3	sepgsql DROP support. ... KaiGai Kohei	14 years ago
Robert Haas	e1042a3484	sepgsql: Check CREATE permissions for some object types. ... KaiGai Kohei, reviewed by Dimitri Fontaine and me.	14 years ago