Red Hat Bugzilla – Bug 782529
Propose that you turn on PrivateTmp=true in service file for pyzor
Last modified: 2015-03-05 18:10:08 EST
I would like to propose using PrivateTmp for pyzor systemd unit file
This should make the use of /tmp directory more secure
and avoid users from being able to potentially effect it.
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.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.
(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)
More information and reason for this action is here:
The pyzor package has as far as I can tell never included a systemd unit file (or a sysvinit script), so I'm not sure why this ticket was even filed.
If I do split out the server component and supply a unit file I'll be sure to to try out PrivateTmp.