Bug 1163420
| Summary: | Adjust log permissions to 0750 for openstack-sahara | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Lon Hohberger <lhh> |
| Component: | openstack-sahara | Assignee: | Elise Gafford <egafford> |
| Status: | CLOSED ERRATA | QA Contact: | Luigi Toscano <ltoscano> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.0 (RHEL 7) | CC: | aberezin, dnavale, matt, nlevinki, sclewis, yeylon |
| Target Milestone: | z4 | Keywords: | EasyFix, ZStream |
| Target Release: | 5.0 (RHEL 7) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-sahara-2014.1.3-2.el7ost | Doc Type: | Bug Fix |
| Doc Text: |
Previously, the log directory permissions for Sahara was set to 755, resulting in the Sahara service not conforming to the Red Hat log security standards.
With this update, the directory permissions are modified to 750, thus, conforming to the Red Hat log security standards.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-04-16 14:37:38 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1163424 | ||
|
Description
Lon Hohberger
2014-11-12 16:42:29 UTC
The intent here is to tighten up access on /var/log directories and files. Note that, apart from the RPM spec files, it's possible some OpenStack components may be setting permissions incorrectly as well. It also may be the case that this component has a valid need to have its /var/log directory world-readable. If that is the case, please close this bugzilla. The permissions of a freshly installed /var/log/sahara are 0750, thanks to the change in the RPM file. Verified on openstack-sahara-2014.1.3-3.el7ost.noarch Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-0825.html |