Hide Forgot
Description of problem: $ sandbox -t sandbox_min_t htop ERROR: could not find datum for type sandbox_t /bin/sandbox: Sandbox Policy is currently disabled. You need to enable the policy by executing the following as root # semodule -e sandbox $ su -c 'semodule -l | grep sand' sandbox 1.0.0 Disabled sandboxX 1.0.0 (htop used as example there ) # semodule -l | grep sand sandbox 1.0.0 sandboxX 1.0.0 After update/reinstall selinux-policy-targeted package this module is disabled again. This behavior is mistaken : "sandbox.pp should be enabled once you enable it, if not then this is a bug in the tooling." (https://lists.fedoraproject.org/pipermail/selinux/2013-August/015751.html) Version-Release number of selected component (if applicable): selinux-policy-targeted Version : 3.12.1 Release : 73.fc19 How reproducible: Steps to Reproduce: # yum install policycoreutils-sandbox # semodule -e sandbox # semodule -l | grep sand (should display: sandbox 1.0.0) # yum reinstall selinux-policy-targeted # semodule -l | grep sand (should display: sandbox 1.0.0 Disabled) Actual results: After update/reinstall selinux-policy-targeted package this module is disabled again. Expected results: # yum reinstall selinux-policy-targeted # semodule -l | grep sand (should display still: sandbox 1.0.0 ) Additional info:
Dan added changes to F20. We need to test them and then we can back port them.
I also need to change the sandbox command to reference this package.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 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 this bug is closed as described in the policy above. 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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.
This bug is _still_ present in Fedora 21. Please re-open the bug report, change the version to F21 and fix-it. Every single time selinux-policy gets updated I have to re-enable sandbox (sometime sandboxX) selinux module.