This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes

Bug 782483

Summary: Propose that you turn on PrivateTmp=true in service file for bluez
Product: [Fedora] Fedora Reporter: Daniel Walsh <dwalsh>
Component: bluezAssignee: Bastien Nocera <bnocera>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: bnocera, dwmw2, marcel
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-01-17 16:12: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:28:37 EST
I would like to propose using PrivateTmp for bluez, to make it more secure
and avoid users from being able to potentially effect it.

http://fedoraproject.org/wiki/Features/ServicesPrivateTmp
Comment 1 Bastien Nocera 2012-01-17 12:39:46 EST
It doesn't use temporary files, so I would rather see SELinux denials than papering over the problem.
Comment 2 Daniel Walsh 2012-01-17 16:12:37 EST
Ok I can remove the label from bluetooth policy and see if they come back.  I was just going through all policy that had tmp_t defined and used init_t.