Bug 120835 - user controlled devices don't activate with selinux enforcing
user controlled devices don't activate with selinux enforcing
Product: Fedora
Classification: Fedora
Component: policy (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Walsh
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2004-04-14 08:21 EDT by Brian G. Anderson
Modified: 2007-11-30 17:10 EST (History)
1 user (show)

See Also:
Fixed In Version: 1.11.1-6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-05-10 14:09:44 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Audit messages in log (14.12 KB, text/plain)
2004-04-14 08:22 EDT, Brian G. Anderson
no flags Details

  None (edit)
Description Brian G. Anderson 2004-04-14 08:21:50 EDT
Description of problem:
I've setup my eth0 device on my DELL laptop to be inactive on bootup,
but user controllable.  When I use system-control-network and try and
activate eth0, the activation window appears and then log starts
filling up with audit messages until I kill the activation window. 
The messages are attached.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. set up eth0 to be inactive on boot, but user controllable
2. reboot
3. use system-control-network to try and active eth0
Actual results:
disk activity as audit messages fill the log

Expected results:
activation of eth0

Additional info:
The same thing happens if I try and use ifup from the command line. If
I become root then I can active the device using ifup.
Comment 1 Brian G. Anderson 2004-04-14 08:22:37 EDT
Created attachment 99399 [details]
Audit messages in log
Comment 2 Harald Hoyer 2004-04-14 08:40:55 EDT
seems like usernetctl needs better selinux policies..
Comment 3 Daniel Walsh 2004-04-15 11:38:21 EDT
Fixed in rawhide.  policy-1.11.1-6

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