Red Hat Bugzilla – Bug 782519
Propose that you turn on PrivateTmp=true in service file for ntop
Last modified: 2012-08-10 18:30:26 EDT
I would like to propose using PrivateTmp for ntop systemd unit file
This should make the use of /tmp directory more secure
and avoid users from being able to potentially effect it.
I haven't debugged this further yet but enabling PrivateTmp doesn't work out of the box:
Jan 22 20:35:09 f17 ntop: **WARNING** gzwrite error (null)(0)
Are you testing on a Rawhide or F16. This will ONLY work on Rawhide with the systemd-38 or greater.
(In reply to comment #2)
> Are you testing on a Rawhide or F16.
Rawhide with systemd-38-4.fc17.x86_64
Ok, any idea what ntop is trying to do?
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.
The latest (5.0) ntop release does work fine with PrivateTmp.
I've built it for rawhide and will probably also do an f17 build
after some more testing.
ntop-5.0-2.fc17 has been submitted as an update for Fedora 17.
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing ntop-5.0-2.fc17'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
ntop-5.0-2.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.