Bug 995779 - Packstack needs to enable more sebools
Summary: Packstack needs to enable more sebools
Alias: None
Product: Fedora
Classification: Fedora
Component: openstack-selinux
Version: 19
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Lon Hohberger
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2013-08-11 02:53 UTC by Sandro Mathys
Modified: 2014-09-03 20:43 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2014-09-03 20:43:43 UTC
Type: Bug

Attachments (Terms of Use)

Description Sandro Mathys 2013-08-11 02:53:31 UTC
Description of problem:
OpenStack causes a few SELinux AVC denials after being installed with Packstack and some could be prevented by enabling two more SELinux Booleans.

Version-Release number of selected component (if applicable):
Current RDO Havana M2 on F19

How reproducible:

Steps to Reproduce:
1. packstack --all-in-one --os-quantum-install=n
2. cat /var/log/audit/audit.log | audit2allow

Actual results:
#============= rsync_t ==============

#!!!! This avc can be allowed using the boolean 'rsync_full_access'
allow rsync_t var_lock_t:dir write;

#============= swift_t ==============
#!!!! This avc can be allowed using the boolean 'nis_enabled'
allow swift_t self:tcp_socket { accept listen };
allow swift_t user_home_dir_t:dir search;
allow swift_t var_t:dir { write remove_name add_name };
allow swift_t var_t:file { rename read lock create write getattr unlink open };
allow swift_t xserver_port_t:tcp_socket name_bind;

Expected results:
No easy to avoid SELinux AVC denials.

Additional info:
There's also a few more denials that are not (yet) covered by booleans, so reporting those seperately against selinux-policy-targeted.

Comment 1 Martin Magr 2013-09-23 14:57:27 UTC
This should be done in openstack-selinux package I guess.

Comment 2 Lon Hohberger 2014-09-03 20:43:43 UTC
We either did this (EPEL RDO) or it doesn't apply to Fedora (which doesn't have openstack-selinux)

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