¡Hola Mathieu!
El 2013-11-21 a las 22:04 +0100, Mathieu MD escribió:
I was trying to follow the code, and it looks like
/usr/lib/kde4/libexec/kcheckpass uses the kdm pam service, which
imports the common services and adds some normal pam stuff. ::
Ups, sorry, that was wrong, it uses the
Hello Maximiliano,
Thanks for still being around my bug report :-)
I don't know if the problem is still reproduceable for you, it was
never reproduceable for me.
I am still using the same machine, and though up-to-date, this bug is
still here. :(
But if you do, could you check the
¡Hola Mathieu!
El 2014-03-28 a las 19:12 +0100, Mathieu MD escribió:
But if you do, could you check the permissions of the
/sbin/unix_chkpwd command?
Permissions on unix_chkpwd seems to be correct with setgid shadow:
-rwxr-sr-x 1 root shadow 35K 02-14 00:27 /sbin/unix_chkpwd*
And the
Muchas gracias Maximiliano!
It was the permissions on /etc/shadow which were root:root 600.
Fixing them to root:shadow 640 made both xscreensaver and kscreensaver
able to log me back in!
I have no idea what may have changed permissions on shadow file, though.
Anyway, thank you very much for
Hi Maximiliano,
I do use kdm to login.
I tried to run xscreensaver as you told, but it did not change anything:
I still cannot login back.
Here is my pam files:
#
# /etc/pam.d/kdm - specify the PAM behaviour of kdm
#
auth required
Hi,
In article 52433f8a.3040...@gmail.com you wrote:
Thanks for your feedback.
It may have been the case the very first day, but now that I had reboot
many times, and still the problem is the same, what could it be?
(sorry for replying late: I did not received your message)
I was trying to
Thanks for your feedback.
It may have been the case the very first day, but now that I had reboot
many times, and still the problem is the same, what could it be?
(sorry for replying late: I did not received your message)
--
Mathieu
I see you also pulled in the libc and pam updates. During
I see you also pulled in the libc and pam updates. During the libc upgrade
there should have been a dialog requesting service restarts for ssh and cupsd
as the upgrade breaks authentication. The wall of text explaining the upgrade
should have stated that X (and therefore kdm) needs to be
8 matches
Mail list logo
