On Mon, Mar 12, 2007 at 02:28:09AM -0400, Albert Cardona wrote: > At least in slock 0.6, nothing prevents me from killing the Xorg server > with control+alt+backspace, returning to an open tty.
No locker should prevent you from killing the x server. If you use startx use startx && exit to prevent such situation, or simply exec startx > Also, I cannot unlock ever: the screen turns black on launching slock, > then I type my password and push return. Slock beeps and that's it, no > unlocking. I have a fingerprint reader enabled that I use on the gnome > side. 'pam' is setup so that sudo does not ask for the finger tip swipe. > I fail to see why should pam interfere with slock, but I can't see any > other source of inteference other than pam. Hmm, dunno which mechanism is used by your fingerprint reader, but slock uses the getpw() mechanism of Unix which is usually similiar to the authentication method in use by login(1). Regards, -- Anselm R. Garbe >< http://www.suckless.org/ >< GPG key: 0D73F361
