[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    Bug#387: Screensaver won't lock (declares shadow passwd is present and is not)
From:       Irish <irish () eskimo ! com>
Date:       1999-02-27 11:27:04
[Download RAW message or body]

Some additional information:
I have upgraded my system to kernel 2.2.1, Util-linux to 2.9h, and KDE 1.1.
This problem still occurs. 

Additionally, another user read my bug report, has the same problem, and mailed
me to see if I had a fix. I said no, but managed to get some system info from
them as well: 
Kernel 2.0.34, Util-linux 2.7.1, and they also have never installed shadow. 

It is clear that the new shadow check code does not always detect the *absence*
of shadow, and breaks locking. 
PLEASE INVESTIGATE, this is not a one-off with one or two screensavers. Klock
is completely broken. I'm hoping this is not a complicated fix; likely a
simple miss or typo somewhere. I'd love to fix it, but I do not write C++. 

Thank you, 
Irish

On Thu, 28 Jan 1999, you wrote:
>>Irish wrote:
>>> 
>>> Package: klock
>>> Version: 0.4
>>> 
>>> Screensaver locking worked normally on my system with KDE ver. 1.0. With
>>> ver. 1.1pre2 it will not lock - it insists that shadow passwords are
>>> installed on my system and they are not. /etc/passwd is world readable.
>>
>>/etc/passwd is always world readable.  Is the second field an 'x'?
>>
>>root:x:0:0:root:/root:/bin/bash
>
>No, it is my root password, encrypted. 
>
>>Shadow passwords are used if configure was run with --enable-shadow
>
>It was not compiled with that option. 
>
>>> The changelog in kscreensaver (kdebase) says:
>>> "1998-12-13  Christian Esken  <esken@kde.org>
>>>         * Calling kcheckpass (only on Shadow systems). This checks if
>>> the password database can be acessed. This uses the new return code (#2)
>>> by kcheckpass."
>>> 
>>> What determines whether shadow is present, and how do I stop it?
>>
>>Did you compile KDE yourself?  If not, find a version that doesn't
>>use shadow passwords or compile it yourself.  Otherwise, I don't
>>have a clue at the moment.
>
>I did compile it myself. 
>
>>Out of curiosity, what happens when you make kcheckpass suid root?
>
>Nothing. I did try that. 
>
>Again, what bit of code determines whether shadow is present, and how does it
>determine this? How can I stop the check? 
>
>Thank you, 
>Irish

[prev in list] [next in list] [prev in thread] [next in thread]