Bug 782483 - Propose that you turn on PrivateTmp=true in service file for bluez
Propose that you turn on PrivateTmp=true in service file for bluez
Product: Fedora
Classification: Fedora
Component: bluez (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Bastien Nocera
Fedora Extras Quality Assurance
Depends On:
Blocks: PrivateTmp
  Show dependency treegraph
Reported: 2012-01-17 10:28 EST by Daniel Walsh
Modified: 2012-01-17 16:12 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-01-17 16:12:37 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
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.

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.

Note You need to log in before you can comment on or make changes to this bug.