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
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: corosync
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Steven Dake
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: PrivateTmp
TreeView+ depends on / blocked
 
Reported: 2012-01-17 15:32 UTC by Daniel Walsh
Modified: 2016-04-26 19:19 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-01-17 16:45:44 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Daniel Walsh 2012-01-17 15:32:55 UTC
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 16:21:30 UTC
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 16:32:10 UTC
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 16:45:44 UTC
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.