Bug 456415 - NetworkManager is not working due to policy restriction
NetworkManager is not working due to policy restriction
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: selinux-policy-targeted (Show other bugs)
8
i686 Linux
low Severity low
: ---
: ---
Assigned To: Daniel Walsh
Ben Levenson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-07-23 09:46 EDT by Matthias Scheutz
Modified: 2008-11-17 17:05 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-11-17 17:05:15 EST
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 Matthias Scheutz 2008-07-23 09:46:56 EDT
Description of problem:

SELinux is preventing NetworkManager (NetworkManager_t) "setsched" to <Unknown>
(NetworkManager_t).

Source Context:  system_u:system_r:NetworkManager_t:s0Target
Context:  system_u:system_r:NetworkManager_t:s0Target Objects:  None [ process
]Source:  NetworkManagerSource
Path:  /usr/sbin/NetworkManagerPort:  <Unknown>Host:  hriSource RPM
Packages:  NetworkManager-0.7.0-0.6.9.svn3675.fc8Target RPM Packages:  Policy
RPM:  selinux-policy-3.0.8-109.fc8Selinux Enabled:  TruePolicy
Type:  targetedMLS Enabled:  TrueEnforcing Mode:  EnforcingPlugin
Name:  catchallHost Name:  hriPlatform:  Linux hri 2.6.25.10-47.fc8 #1 SMP Mon
Jul 7 18:39:51 EDT 2008 i686 i686Alert Count:  1First Seen:  Wed 23 Jul 2008
09:31:13 AM EDTLast Seen:  Wed 23 Jul 2008 09:31:13 AM EDT

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Daniel Walsh 2008-08-01 11:03:13 EDT
Fixed in selinux-policy-3.0.8-111.fc8
Comment 2 Daniel Walsh 2008-11-17 17:05:15 EST
Closing all bugs that have been in modified for over a month.  Please reopen if the bug is not actually fixed.

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