Bug 451720 - After update, NetworkManager raises SELinux denials, does not access keyring.
Summary: After update, NetworkManager raises SELinux denials, does not access keyring.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 9
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-06-16 21:17 UTC by August Schwerdfeger
Modified: 2008-07-16 02:12 UTC (History)
2 users (show)

Fixed In Version: selinux-policy-3.3.1-74.fc9
Clone Of:
Environment:
Last Closed: 2008-07-16 02:12:45 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Diagnostics from 'setroubleshootd'. (7.62 KB, text/plain)
2008-06-16 21:17 UTC, August Schwerdfeger
no flags Details

Description August Schwerdfeger 2008-06-16 21:17:08 UTC
Description of problem:

After an update of the NetworkManager package, when I log in, three SELinux
denials are raised on NetworkManager's account, and NetworkManager does not
attempt to access the GNOME keyring unless I explicitly select a wireless
network for which such is required.

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

NetworkManager-0.7.0-0.9.4.svn3675.fc9.i386


How reproducible:

Set up a wireless network with a secret stored inside the GNOME keyring.
Password-protect the keyring. Log in with that network being the default to
which to connect.

Expected results:

Before the update, immediately upon login, a dialog would pop up requesting the
password for the keyring. This password being given, NetworkManager would
connect to the secret-protected network.

Actual results:

After the update, when I log in, three SELinux denials are raised. No keyring
password prompt occurs and NetworkManager automatically connects to a network
for which secrets are not required. If I then explicitly select the
secret-protected network, the password prompt comes up and connection proceeds
as usual.

Additional info:

I attach information about the three denials raised by SELinux. Switching
SELinux to "permissive" mode does not alter the situation.

Comment 1 August Schwerdfeger 2008-06-16 21:17:08 UTC
Created attachment 309539 [details]
Diagnostics from 'setroubleshootd'.


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