Bug 782492 – Propose that you turn on PrivateTmp=true in service file for corosync

Bug 782492 - Propose that you turn on PrivateTmp=true in service file for corosync

Summary:	Propose that you turn on PrivateTmp=true in service file for corosync

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	corosync (Show other bugs)
Sub Component:
Version:	rawhide
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	---
Target Release:	---
Assigned To:	Steven Dake
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	PrivateTmp
	Show dependency tree / graph

Reported:	2012-01-17 10:32 EST by Daniel Walsh
Modified:	2016-04-26 15:19 EDT (History)
CC List:	4 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2012-01-17 11:45:44 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Daniel Walsh 2012-01-17 10:32:55 EST

I would like to propose using PrivateTmp for corosync, to make it more secure
and avoid users from being able to potentially effect it.

http://fedoraproject.org/wiki/Features/ServicesPrivateTmp

Comment 1 Steven Dake 2012-01-17 11:21:30 EST

Dan,

Corosync doesn't create/open/delete any files in /tmp or /var/tmp on Fedora.  The cman plugins may do this, so I've copied Fabio (cman maintainer), but we are removing cman in Fedora 17.  On Fedora, we use /var/lib/corosync and /dev/shm exclusively.  If you can show me evidence of the corosync process using /var/tmp we can consider this feature.  Searching the code base doesn't show any code using this directory and running through strace doesn't demonstrate access to these directories either.

Thanks
-steve

Comment 2 Daniel Walsh 2012-01-17 11:32:10 EST

Steve, all I did was search the SELinux policy for domains that used tmp, if corosync no longer uses /tmp then you can close this bug.

One other thing that could cause this would be bash redirection.

command << _EOF
STUFF
__EOF

Anyways if you don't think you use /tmp then close the bug.

Comment 3 Steven Dake 2012-01-17 11:45:44 EST

We did use /var/tmp at one time but changed to shm_open for more secure operation.

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