Hide Forgot
Description of problem: If you do run for example 'semanage permissive -a permissive' an invalid te file will be generated a left in /var/lib/selinux (I think) and then if you try to run 'semanage permissive -a <type>' again it will fail because it tries to compile the bad te file previously generated. Version-Release number of selected component (if applicable): policycoreutils-python-2.0.83-19.30.el6.x86_64 How reproducible: Steps to Reproduce: 1.semanage permissive -a permissive 2.semanage permissive -a secadm_t 3. Actual results: step 2 fails because step 1 failed Expected results: Additional info:
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux.
Fixed in policycoreutils-2.1.14-89.el7
Yes, we have #semanage permissive -a permissive ValueError: permissive is not a domain type
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux release for currently deployed products. This request is not yet committed for inclusion in a release.
Now it seems to be broken a bit: (even without trying the command with nonexisting type before) # rpm -qa policycoreutils\* policycoreutils-python-2.0.83-19.41.el6.x86_64 policycoreutils-2.0.83-19.41.el6.x86_64 # semanage permissive -a httpd_t /usr/sbin/semanage: httpd_t is not a domain type
(In reply to Michal Trunecka from comment #8) > Now it seems to be broken a bit: > > (even without trying the command with nonexisting type before) > > # rpm -qa policycoreutils\* > policycoreutils-python-2.0.83-19.41.el6.x86_64 > policycoreutils-2.0.83-19.41.el6.x86_64 > # semanage permissive -a httpd_t > /usr/sbin/semanage: httpd_t is not a domain type strange, it works on Fedora with the same patch. Need to re-check it.
Ok, I found a bug.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-1569.html