Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 451720 - After update, NetworkManager raises SELinux denials, does not access keyring.
Summary: After update, NetworkManager raises SELinux denials, does not access keyring.
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 9
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
Depends On:
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
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-07-16 02:12:45 UTC

Attachments (Terms of Use)
Diagnostics from 'setroubleshootd'. (deleted)
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):


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.