Security-Enhanced PostgreSQL is up for package review (#249522) and depends on some policy changes that cannot be incorporated in policy modules. A request was made to Chris PeBenito to incorporate these changes into reference policy, here: http://marc.info/?l=selinux&m=118597087013327&w=2 Dan Walsh indicated his preference that these changes be included upstream rather than as a patch for Fedora's policy: <dwalsh:#selinux> Method, I would prefer they come from upstream. I am creating this bug to track this issue, indicate that a user desires this enhancement, and to have the Security-Enhanced PostgreSQL package review block on it.
http://marc.info/?l=selinux&m=118666527208126&w=2 The definitions of object classes and permissions for SE-PostgreSQL got merged into the upstreamed reference policy.
The selinux-policy-3.0.6-1 or later got the object classes definition for SE- PostgreSQL. Rob, can you close ths issue? --- selinux-policy.spec 21 Aug 2007 20:08:22 -0000 1.501 +++ selinux-policy.spec 22 Aug 2007 14:46:21 -0000 1.502 @@ -16,8 +16,8 @@ %define CHECKPOLICYVER 2.0.3-1 Summary: SELinux policy configuration Name: selinux-policy -Version: 3.0.5 -Release: 11%{?dist} +Version: 3.0.6 +Release: 1%{?dist} License: GPL Group: System Environment/Base Source: serefpolicy-%{version}.tgz @@ -172,7 +172,7 @@ %description SELinux Reference Policy - modular. -Based off of reference policy: Checked out revision 2370. +Based off of reference policy: Checked out revision 2393. %prep %setup -q -n serefpolicy-%{version}
selinux-policy-3.0.6-1 has not yet built correctly, so this is not quite resolved yet.
3.0.6-1.fc8 is already in koji repo and can we close this now? http://koji.fedoraproject.org/koji/buildinfo?buildID=15255
I also think it is the time to close the issue.
(In reply to comment #5) > I also think it is the time to close the issue. Okay, now closing.