| Summary: | pam module does not start active session | ||
|---|---|---|---|
| Product: | ConsoleKit | Reporter: | Hans Freitag <zem> |
| Component: | PAM module | Assignee: | Martin Pitt <martin.pitt> |
| Status: | NEW --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | CC: | lennart, william.jon.mccann |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: | pam module should start an active session | ||
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 91001 [details] pam module should start an active session I wrote a patch to the pam-ck-connector so that the created session is active, because I think this solves some of the bugs listed to the package in the debian bts for consolekit and various display managers. The bigest advantage is that you can use any Display Manager other than gdm again by creating an active session via pam. The other DMs previously used ck-launch-session at user level to create an active session but this is not possible anymore due to security risks. - I added the parameter active to the ck-connector library call to work like described in the consolekit dbus description. - I modified the pam module to launch an active session - I added a nonactive parameter to the pam module - I updated the manpage The patch is attached to this bugreport. I hope this does not raise to much new security issues, but i don't see a point against from my perspective. regards Hans