Bug 505452
Summary: | Shorewall prevented from starting at boot time | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Bill Gradwohl <bill> |
Component: | selinux-policy | Assignee: | Daniel Walsh <dwalsh> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 11 | CC: | dwalsh, jkubin, mgrepl |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-11-18 13:09:55 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Bill Gradwohl
2009-06-11 23:19:52 UTC
Failed to mention that Shorewall starts fine via service shorewall start after the initial boot sequence finishes and you're able to login and enter that command manually. Fixed in selinux-policy-3.6.12-50.fc11.src.rpm You can allow this for now by executing # grep shorewall /var/log/audit/audit.log | audit2aloow -M myshorewall # semodule -i myshorewall.pp |