Bug 161862 - target policy is not compatible with the latest hal
target policy is not compatible with the latest hal
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: selinux-policy-targeted (Show other bugs)
4
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Walsh
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-06-27 17:37 EDT by Sergey V. Udaltsov
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version: 1.25.1-7
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-08-19 04:28:02 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Sergey V. Udaltsov 2005-06-27 17:37:28 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4

Description of problem:
hal contains wireless mouse battery addon (/usr/libexec/hald-addon-usb-csr). It requires access to usbvfs - which current selinux policy does not provide. I had to add the following lines to the policy:

allow hald_t usbfs_t:dir read;
allow hald_t usbfs_t:file { ioctl write };

With these settings addon works ok - without them I get constant "access denied" selinux messages in the syslog. Could you please add these 2 lines to the policy?

Version-Release number of selected component (if applicable):
hal-0.5.2-2 selinux-policy-targeted-1.23.18-12

How reproducible:
Always

Steps to Reproduce:
1. Attach Logitech MX 1000 mouse to the PC with hal running
2. Look at the hal properties.
  

Actual Results:  You don't get proper battery.charge_level.current for the mouse device,
"access denied" messages in the syslog

Expected Results:  battery.charge_level.current filled with the current level

Additional info:
Comment 1 Daniel Walsh 2005-07-11 14:22:37 EDT
Fixed in selinux-policy-targeted-1.25.1-7

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