Hi, * Moritz Wilhelmy <c...@wzff.de> [2009-12-20 16:16]: > On Sun, Dec 20, 2009 at 12:29:48PM +0100, markus schnalke wrote: > > [2009-12-20 12:03] Moritz Wilhelmy <c...@wzff.de> > > > On Sun, Dec 20, 2009 at 11:53:02AM +0100, markus schnalke wrote: > > > > > > > > Maybe we could give slock a system account to check the password > > > > against. Thus it must not to be the own account, but can be a special > > > > slock system user, which exists just for this task. > > > > > > > > Unfortunately only root users will have the ability to set different > > > > passwords then. > > > > > > And only root-users will be able to use slock then, so it doesn't > > > work for people working on public machines, for instance at university. > > > > They still can use it with their account password, but not with a > > different one. > > > > It is no solution to the problem. It was more a thought to the topic. > > doesn't work at my university because we have NIS shared accounts > and afaik slock just reads shadow
No this is wrong, it's using getpw*() which is querying the name service switch (nss). Cheers Nico -- Nico Golde - http://www.ngolde.de - n...@jabber.ccc.de - GPG: 0xA0A0AAAA For security reasons, all text in this mail is double-rot13 encrypted.
pgpsfF6aqBvW1.pgp
Description: PGP signature
