| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I looked around in the gdm code and don't see anything obvious
that would make it not work with CK2, and google turned up nothing
useful. I did notice that PCLinuxOS is using gdm-2.20.11 as well,
but aside from a special dbus config file (which I tried here with
no change to behavior), I don't see anything special that they do.
They use PAM though, so maybe that makes a difference.
These days, I don't even use gdm any more - I'm on xdm with
alienBOB's config (slightly modified) from his livecd work. The
only things that users might miss are a session chooser (change
$HOME.xinitrc instead) and switching users (I don't like that
anyway), so good riddance to this one.
Signed-off-by: Robby Workman <rworkman@slackbuilds.org>
Signed-off-by: Willy Sudiarto Raharjo <willysr@slackbuilds.org>
|
| |
|
|
|
|
|
| |
This commit also adds a few more files in sysconfdir to the
config() handling (with .new extensions).
Signed-off-by: Robby Workman <rworkman@slackbuilds.org>
|
| |
|
|
|
|
|
| |
Thanks to Andrzej Telszewski for the report and thanks
to mancha for his quick response with the fix.
Signed-off-by: Robby Workman <rworkman@slackbuilds.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Starting with glibc 2.17 (eglibc 2.17), crypt() fails with
EINVAL (w/ NULL return) if the salt violates specifications.
Additionally, on FIPS-140 enabled Linux systems, DES or MD5
encrypted passwords passed to crypt() fail with EPERM (w/
NULL return).
Slackware-current has transitioned to glibc 2.17 and as you
might be aware from reading my posts on LQ, I have dedicated
time to fixing userland which does not adequately handle
crypt() returns given the new behavior.
gdm is negatively affected and my attached patch (against
gdm 2.20.11) addresses this.
This is in anticipation of a new Slackware release but can
be applied to the SBo package for Slackware 14.0 since it is
backwards compatible and should not affect behavior on glibc
2.15. It would be good if my assertion were tested.
[rworkman] Yeah, it seems to work here :-)
Signed-off-by: Robby Workman <rworkman@slackbuilds.org>
|
|
|
Signed-off-by: Robby Workman <rworkman@slackbuilds.org>
|
