Red Hat Bugzilla – Bug 782492
Propose that you turn on PrivateTmp=true in service file for corosync
Last modified: 2016-04-26 15:19:44 EDT
I would like to propose using PrivateTmp for corosync, to make it more secure
and avoid users from being able to potentially effect it.
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.
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
Anyways if you don't think you use /tmp then close the bug.
We did use /var/tmp at one time but changed to shm_open for more secure operation.