Bug 782501

Summary: Propose that you turn on PrivateTmp=true in service file for dspam
Product: [Fedora] Fedora Reporter: Daniel Walsh <dwalsh>
Component: dspamAssignee: Nathanael Noblet <nathanael>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: nathanael
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-16 12:29:37 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 782466    

Description Daniel Walsh 2012-01-17 10:41:43 EST
I would like to propose using PrivateTmp for dspam systemd unit file
This should make the use of /tmp directory more secure
and avoid users from being able to potentially effect it.

Comment 1 Daniel Walsh 2012-02-06 15:45:44 EST
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.
Comment 2 Nathanael Noblet 2012-02-16 12:29:37 EST
Sorry for the delay, I actually added it the day you posted the bug, however testing if it worked ran into /usrmove issues, and then F17 live nightlies not installing correctly etc...

It seems that dspam works fine with the PrivateTmp directory (at least it starts up fine).