Bug 1234266

Summary: Use safer permission when storing ringid
Product: Red Hat Enterprise Linux 7 Reporter: Jan Friesse <jfriesse>
Component: corosyncAssignee: Jan Friesse <jfriesse>
Status: CLOSED ERRATA QA Contact: cluster-qe <cluster-qe>
Severity: high Docs Contact:
Priority: high    
Version: 7.1CC: ccaulfie, cluster-maint, jkortus
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: corosync-2.3.4-6.el7 Doc Type: Bug Fix
Doc Text:
This BZ doesn't need doc text.
 Story Points: ---
Clone Of:
: 1417907 (view as bug list) Environment:
Last Closed: 2015-11-19 11:41:55 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: 1417907    
Attachments:
Description Flags
corosync_ring_id_store: Use safer permissions none

Description Jan Friesse 2015-06-22 08:45:54 UTC 
corosync_ring_id_store should use same (safer) permissions as
corosync_ring_id_create_or_load for (eventually) newly created ringid
file.

Unit test:
- Start corosync on two nodes
- Delete /var/lib/corosync/ringid* on one of node
- Shutdown corosync on second node

- Check permission of /var/lib/corosync/ringid* on first node.

Before patch:
-> -rwxr-xr-x

After patch:
-> -rwx-----
Comment 1 Jan Friesse 2015-06-22 08:46:39 UTC 
Created attachment 1041653 [details]
corosync_ring_id_store: Use safer permissions

corosync_ring_id_store: Use safer permissions

corosync_ring_id_store should use same (safer) permissions as
corosync_ring_id_create_or_load for (eventually) newly created ringid
file.

Credit to Sjerek for finding this problem.

Signed-off-by: Jan Friesse <jfriesse>
Reviewed-by: Christine Caulfield <ccaulfie>
Comment 5 errata-xmlrpc 2015-11-19 11:41:55 UTC 
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-2354.html