| Summary: | SELinux policy for keystone | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mark McLoughlin <markmc> |
| Component: | openstack-keystone | Assignee: | Alan Pevec (Fedora) <apevec> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 17 | CC: | apevec, apevec, bfilippov, breu, dmalcolm, dwalsh, ivazqueznet, jonathansteffan, markmc, matt_domsch, mgrepl, p, rbryant, tomspur |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-12-18 18:21:18 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Mark McLoughlin
2011-12-05 11:30:06 UTC
To confirm that the keystone service runs in the initrc_t domain: system_u:system_r:initrc_t:s0 20646 ? 00:00:01 keystone-all Why is openstack-keystone using /tmp? Why is it writing content that can execute? It should be using /var/run for this or at least use privatetmp in unit file. Policy is in selinux-policy-3.10.0-98.fc17 But needs lots of testing, since all I did was write it and start and stop the service. Not sure how it interacts with other openstack daemons. (In reply to comment #2) > Why is openstack-keystone using /tmp? Why is it writing content that can > execute? It should be using /var/run for this or at least use privatetmp in > unit file. That's probably Python's uuid issue bug 814391 (In reply to comment #4) > (In reply to comment #2) > > Why is openstack-keystone using /tmp? Why is it writing content that can > > execute? It should be using /var/run for this or at least use privatetmp in > > unit file. > > That's probably Python's uuid issue bug 814391 This is fixed in Fedora; see https://bugzilla.redhat.com/show_bug.cgi?id=814391#c10 This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. |