Bug 217845 - setools can't open version 21 policies
Summary: setools can't open version 21 policies
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: setools
Version: 5.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Daniel Walsh
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-11-30 11:44 UTC by Bastien Nocera
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

Fixed In Version: RC
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-02-08 01:06:38 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Bastien Nocera 2006-11-30 11:44:32 UTC
+++ This bug was initially created as a clone of Bug #212807 +++

apol/seaudit/sediffx/etc. can't open policy.21 file (they all give me variations
on "The selected file does not appear to be a valid SELinux Policy").

-- Additional comment from dwalsh on 2006-10-30 15:38 EST --
Fixed in setools-3.0-2.fc6


Can be reproduced on RHEL5 beta2:
selinux-policy-2.4.3-8.el5
libselinux-1.30.29-2
libselinux-python-1.30.29-2
selinux-policy-targeted-2.4.3-8.el5
libselinux-devel-1.30.29-2
setools-2.4-2.1

# seinfo -A || echo "Failed"
Failed
# sediff /etc/selinux/targeted/policy/policy.21 
Problem opening first policy file: /etc/selinux/targeted/policy/policy.21

Comment 1 RHEL Program Management 2006-11-30 12:00:44 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 2 Daniel Walsh 2006-11-30 17:39:32 UTC
Fixed in setools-3.0-3

Comment 3 Jay Turner 2007-01-11 03:52:26 UTC
QE ack for RHEL5.

Comment 4 RHEL Program Management 2007-02-08 01:06:38 UTC
A package has been built which should help the problem described in 
this bug report. This report is therefore being closed with a resolution 
of CURRENTRELEASE. You may reopen this bug report if the solution does 
not work for you.



Note You need to log in before you can comment on or make changes to this bug.