Red Hat Bugzilla – Bug 782471
Propose that you turn on PrivateTmp=true in service file for Zarafa
Last modified: 2012-02-06 15:54:49 EST
I would like to propose using PrivateTmp for Zarafa, to make it more secure
and avoid users from being able to potentially effect it.
I am tempted to use /var/lib/zarafa/autoresponder (or similar) instead of
/tmp, because /tmp is on recent Fedora anyway on a ramfs, thus /tmp gets
emptied out during reboots and all set up autoresponder history data are
gnone, too. It's anyway not really temporary data, but application created
data that should exist as long as it's needed. Objections?
No that would be perfect. I don't believe any privileged process should use /tmp.
/tmp is for users /var/lib and /run are for system processes...
Any change on this bug. We are coming up to Feature Freeze, and would like some comment on this bug.
If you do not believe this application uses /tmp than please comment on this and close the bug.
If you believe this application needs to use /tmp to communicate with other applications or users then you can close this bug with that comment.
If your app does not use systemd, then close this bug with that comment.
If you have no idea, then please add a comment, and change the bug to assigned.
I need to update the status on this feature.
Thanks for your help.
Zarafa does not yet use systemd. The usage of /tmp is not related to the
initscript, however there might be a /tmp usage of the initscript which I
need to discuss with upstream anyway. But can't be solved without systemd
switching for now anyway.