Bug 905486 - setools - apol will not load valid policy
Summary: setools - apol will not load valid policy
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: setools
Version: 18
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Chris PeBenito
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-29 13:58 UTC by Richard Haines
Modified: 2014-02-05 23:19 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 23:19:15 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Patch that fixes the problem (31.25 KB, patch)
2013-01-29 13:58 UTC, Richard Haines
no flags Details | Diff

Description Richard Haines 2013-01-29 13:58:33 UTC
Created attachment 689843 [details]
Patch that fixes the problem

Description of problem:
The APOL policy analysis app will not load a valid policy

Version-Release number of selected component (if applicable):

setools-3.3.7-31.fc18.x86_64.rpm

How reproducible:
Always

Steps to Reproduce:
1. yum install setools*
2.load apol
3.Try loading a valid selinux policy
  
Actual results:
Error box shown

Expected results:
Load policy

Additional info:
Have a fix for the problem based on a patch that was submitted to the SELinux mailing list. The patch is attached.

Comment 1 cs 2013-02-26 01:38:12 UTC
I have tried applying the patch above to both the 3.3.7-31 source and to the 3.3.8 setools package from tresys.com;  in both cases, an error box appears when I start apol on either the mls or targeted policy.27 in /etc/selinux/:

invalid command name "new_qpol_bool_t"
invalid command name "new_qpol_bool_t"
    while executing
"new_qpol_bool_t $::ApolTop::qpolicy $bool"
    (procedure "Apol_Cond_Bools::open" line 11)
    invoked from within
"[lindex $tab 0]::open $ppath"
    (procedure "_toplevel_policy_open" line 4)
    invoked from within
"_toplevel_policy_open $ppath"
    (procedure "ApolTop::openPolicyPath" line 12)
    invoked from within
"ApolTop::openPolicyPath _70746d0200000000_p_apol_policy_path"
    ("after" script)

Am I doing something wrong or is the patch incomplete?

Comment 2 Daniel Walsh 2013-02-26 16:57:48 UTC
Fixed in setools-3.3.7-34.fc18

Comment 3 Daniel Walsh 2013-02-26 21:59:34 UTC
cs  I believe that patch is applied to the RHEL/Fedora source.  We have quite a few patches.

Comment 4 Fedora End Of Life 2013-12-21 15:44:13 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2014-02-05 23:19:15 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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