Version: unspecified (using KDE 4.4.4) OS: Linux I set server (tested Slackware ver 11.x to 13.x) with multiaccess to KDE (they can login only via KDM) but I cant set password policy for all user using the server because...on the file /usr/include/kgreeterplugin.h is to TODO /** * Contexts the talker can be used in: * - Login: kdm login dialog * - Shutdown: kdm shutdown dialog * - Unlock: kdm unlock dialog (TODO) * - ChangeTok: kdm password change dialog (TODO) * - ExUnlock: kdesktop_lock unlock dialog * - ExChangeTok: kdepasswd password change dialog (TODO) * * The Ex* contexts exist within a running session; the talker must know * how to obtain the currently logged in user (+ domain/realm, etc.) * itself (i.e., fixedEntity will be null). The non-Ex variants will have * a fixedEntity passed in. */ enum Context { Login, Shutdown, Unlock, ChangeTok, ExUnlock, ExChangeTok }; Reproducible: Always Steps to Reproduce: Set Default runlevel : id 4 (/etc/inittab) Start KDM login On the console create account testuser set password for testuser On the KDM login console (tty7) login to account testuser logout testuser from console as the user root do chage -d 0 testuser Switch to KDM console login (tty7) and try login to KDE. Actual Results: When administrator has decided to change the password for user and enforce it on the next login user "testuser" got information: You are required to change your password immediately (root enforced) (administrator has decided to change the password) but there is no any box to change the password. Expected Results: I need enforce change password for a users before they login to KDE
fascinating timing ... *** This bug has been marked as a duplicate of bug 245421 ***
(In reply to comment #1) > fascinating timing ... > > *** This bug has been marked as a duplicate of bug 245421 *** Thanks for replaying. Maybe..., I used "Search for Duplicates" before adding the bug and I still search solution for the trouble. I don`t want use PAM or any other things witch come from no Slackware repositories. Best regards.
oh, without PAM, things get a lot more interesting ... this is indeed not implemented (though in an entirely different place) and - as far as i'm concerned - it's not going to be implemented. we'll see what the other report turns out to be ...
I wrote thread http://www.linuxquestions.org/questions/slackware-14/kdm-change-your-password-immediately-815878/ We are interesting about this implementation. A lot of Slackware servers offers only KDE environment for ordinary users to work with office applications.
well, you'll have to do it yourself ... the place to start is kdebase/workspace/kdm/backend/client.c (both hits for "todo"). you basically need to copy the low-level password changing code from login (or passwd) and integrate it with the callback architecture, so the whole process looks like a PAM conversation from the frontend's POV. you may find someone to help you in the openbsd camp - they are also refusing to use PAM.