Bug 782508

Summary:	Propose that you turn on PrivateTmp=true in service file for xl2tpd
Product:	[Fedora] Fedora	Reporter:	Daniel Walsh <dwalsh>
Component:	xl2tpd	Assignee:	Paul Wouters <pwouters>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	extras-orphan, pwouters
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-02-28 19:54:19 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	782466

Description Daniel Walsh 2012-01-17 15:47:55 UTC

I would like to propose using PrivateTmp for l2tpd systemd unit file
This should make the use of /tmp directory more secure
and avoid users from being able to potentially effect it.

http://fedoraproject.org/wiki/Features/ServicesPrivateTmp

Comment 1 Daniel Walsh 2012-02-06 20:46:16 UTC

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 Paul Wouters 2012-02-28 02:28:46 UTC

I don't think this daemon needs to write in /tmp at all.

The only place where this daemon does need to write is /var/run/ to create the l2tp-socket with which users talk to the daemon (/var/run/xl2tpd/l2tp-socket)

Comment 3 Daniel Walsh 2012-02-28 19:54:19 UTC

I think at one time the sock file was in /tmp.  I will clean up the policy and close this bug.