| 1 |
pambase-20101024-r2 will restore the same behavior as pambase-20101024 |
| 2 |
had; it will restore the 'nox11' argument to the pam_ck_connector.so |
| 3 |
line in /etc/pam.d/system-login. |
| 4 |
|
| 5 |
this pam_ck_connector.so module is now used only for console logins |
| 6 |
because all of the display managers we ship, have native ConsoleKit |
| 7 |
support now: |
| 8 |
|
| 9 |
xdm since 1.1.11-r1 |
| 10 |
slim since 1.3.2-r7 |
| 11 |
lxdm, all versions |
| 12 |
gdm, all versions |
| 13 |
kdm, all versions |
| 14 |
lightdm, all versions |
| 15 |
enter, lastrited now |
| 16 |
|
| 17 |
in practise this means you don't need the CONFIG_AUDITSYSCALL in kernel |
| 18 |
for any of these display managers, or worry about pam_ck_connector.so at |
| 19 |
all. |
| 20 |
|
| 21 |
it also means you don't need to manually put 'ck-launch-session' |
| 22 |
anywhere in your configs, except when using startx with custom .xinitrc. |
| 23 |
and even startx works if you have XSESSION exported and no .xinitrc |
| 24 |
without adding ck-launch-session anywhere yourself. |
| 25 |
|
| 26 |
in otherwords, everything will just work(tm). |
| 27 |
long as people now remember to punt any custom trickery they might have |
| 28 |
added before we reached this point. |
Archives