Red Hat Bugzilla – Bug 228557
LSPP: In labeled ipsec, permissions are checked after deleting the policy
Last modified: 2010-10-22 08:59:23 EDT
Description of problem:
In labeled ipsec, we check to see if selinux grants permissions to delete the
policy after the policy has been scheduled to be deleted. We should check
permissions first, and then delete the policy if granted.
Occurs everytime you delete a labeled ipsec policy.
Steps to Reproduce:
1.Create a labeled ipsec policy.
2.Delete the labeled ipsec policy as someone who should not be able to.
Policy is deleted, regardless of permissions.
Policy should be deleted if permissions granted.
I will be taking the responcibility for this bug and hopefully will have a patch
today. There is no fix in LSPP.65
Fix is present in LSPP .66 and later. Pushed upstream
will submit after accepted into an upstream tree.
Tested in lspp 68 kernel and works great!
This request was evaluated by Red Hat Kernel Team for inclusion in a Red
Hat Enterprise Linux maintenance release, and has moved to bugzilla
A fix for this issue should have been included in the packages contained in the
RHEL5.1-Snapshot3 on partners.redhat.com.
Requested action: Please verify that your issue is fixed as soon as possible to
ensure that it is included in this update release.
After you (Red Hat Partner) have verified that this issue has been addressed,
please perform the following:
1) Change the *status* of this bug to VERIFIED.
2) Add *keyword* of PartnerVerified (leaving the existing keywords unmodified)
If this issue is not fixed, please add a comment describing the most recent
symptoms of the problem you are having and change the status of the bug to FAILS_QA.
More assistance: If you cannot access bugzilla, please reply with a message to
Issue Tracker and I will change the status for you. If you need assistance
accessing ftp://partners.redhat.com, please contact your Partner Manager.
Verified that this is fixed.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.