Bug 1049817
| Summary: | neutron-dhcp-agent fails to start with plenty of SELinux AVC denials | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Kashyap Chamarthy <kchamart> | ||||
| Component: | selinux-policy | Assignee: | Miroslav Grepl <mgrepl> | ||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 20 | CC: | chrisw, dominick.grift, dwalsh, lars, lbezdick, lhh, lvrabec, mgrepl, yeylon | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | 1049807 | Environment: | |||||
| Last Closed: | 2015-06-30 00:50:08 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1049807 | ||||||
| Attachments: |
|
||||||
|
Description
Kashyap Chamarthy
2014-01-08 09:52:16 UTC
Fixed in selinux-policy-3.12.1-113.fc20 Created attachment 847302 [details]
audit.log containing AVC messages from an all-in-one RDO install on F20
With selinux-policy-3.12.1.113 installed:
# rpm -q selinux-policy
selinux-policy-3.12.1-113.fc20.noarch
Using a "packstack --allinone" install, I still get the following from "audit2allow -a":
#============= neutron_t ==============
allow neutron_t file_t:dir mounton;
allow neutron_t netutils_exec_t:file { read execute open execute_no_trans };
allow neutron_t root_t:dir mounton;
allow neutron_t self:capability { net_raw dac_override };
allow neutron_t self:netlink_route_socket nlmsg_write;
allow neutron_t self:packet_socket { bind create getattr };
allow neutron_t self:process setcap;
allow neutron_t sysctl_net_t:dir search;
allow neutron_t sysctl_net_t:file { write getattr open };
allow neutron_t sysfs_t:filesystem unmount;
#!!!! This avc can be allowed using the boolean 'nis_enabled'
allow neutron_t unreserved_port_t:tcp_socket name_bind;
allow neutron_t var_run_t:dir mounton;
allow neutron_t var_run_t:file { read create open mounton };
#============= rsync_t ==============
#!!!! This avc can be allowed using the boolean 'rsync_full_access'
allow rsync_t var_lock_t:dir { write add_name };
#!!!! This avc can be allowed using the boolean 'rsync_full_access'
allow rsync_t var_lock_t:file { write create };
#============= swift_t ==============
allow swift_t file_t:dir { write getattr read create open add_name };
allow swift_t tmpfs_t:dir { write remove_name add_name };
allow swift_t tmpfs_t:file { write getattr link read create unlink open };
allow swift_t tmpfs_t:filesystem getattr;
allow swift_t xserver_port_t:tcp_socket name_bind;
I have attached the raw audit.log. Obviously this covers more than just neutron.
We have ifconfig_var_run_t labeling for /run/netns but it was for ifconfig_domtrans(neutron_t) case which we needed to change to ifconfig_exec(neutron). Did ifconfig access the /run/netns directory? I think we need to change the label - neutron_var_run_t for example. Also not sure if we need all domain transition change to exec. The 'ip' command is what's used to set up network namespaces, so I assume it will certainly access /run/netns - but I've not checked. The important thing is that /run/netns probably isn't right to be neutron_var_run_t, as it's possible to use network namespaces outside of neutron's usage. Yes, 'ip netns add/delete/etc' accesses /run/netns. On F19 and prior (incl. RHEL6), it was accessing /var/run/netns. On RHEL6/CentOS 6, you would not see this since neutron ran in an unconfined domain, IIRC. This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. |