Bug 254164 - gdm should use pam_selinux instead of doing its own selinux code
gdm should use pam_selinux instead of doing its own selinux code
Product: Fedora
Classification: Fedora
Component: gdm (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Ray Strode [halfline]
Fedora Extras Quality Assurance
: Reopened
Depends On:
Blocks: F8Blocker
  Show dependency treegraph
Reported: 2007-08-24 11:16 EDT by Ray Strode [halfline]
Modified: 2007-11-30 17:12 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-10-01 17:23:26 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Ray Strode [halfline] 2007-08-24 11:16:34 EDT
One problem that we're hitting with pam_gnomekeyring is that it runs in the
locked down xdm context since we don't do a domain transition until after pam
session modules are run.  This causes problems because it means
gnome-keyring-daemon runs under the wrong context.

Some session modules (like pam_console) need to run under the xdm domain and not
the user domain though.

If we switch to using pam_selinux then we can partition the session modules to
half run in the xdm context and half in the user context.
Comment 1 Ray Strode [halfline] 2007-08-24 11:34:31 EDT
should be fixed (or really broken) in tomorrow's rawhide
Comment 2 Ray Strode [halfline] 2007-09-07 12:08:46 EDT
it broke things for xguest users.  we need to save, reset and restore the
context around the call to the PreSession script
Comment 3 Ray Strode [halfline] 2007-10-01 17:23:26 EDT
we fixed this a while ago I believe.

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