From: achim@techfak.uni-bielefeld.de (Achim Neumann) Subject: Re: xlock is useless! Date: Thu, 1 Apr 1993 15:32:58 GMT
In article <1993Apr01.091919.31903@aixrs0.hrz.uni-essen.de>, hank@Blimp (Hendrik G. Seliger) writes:
|> There's this nice program called "xlock", which allows to lock an
|> X-console while sleeping in some other corner to keep bad people from
|> doing their job. The only problem under XFree1.2 is that it's still
|> possible to switch VCs. Now if I startx on tty1, it is just as simple
|> as pressing Alt-Ctrl-F1 followed by a Ctrl-C to stop X and get the
|> users login-shell. No password required.
|>
|> I guess it's easy to see that I don't like this. Thus:
|>
|> Question: Does anyone know a workaround to also lock people from
|> switching to other VCs (at least the one X has been started from)??
|>
|> Hank.
|>
|> --
|> ----------------------------------------------------------------------
|> Hendrik G. Seliger Universitaet Essen
|> hank@Blimp.automat.uni-essen.de Schuetzenbahn 70
|> Tel.: +49-201-183-2898 4300 Essen, Germany
|> ----------------------------------------------------------------------
-- I don't think xlock is useless. xlock is designed to protect your X-Session, it can't protect your text sessions at a virtuell console. If you run startx in the background and use a tool to lock your text session (I don't know one in the moment, but I think there are some) your X-Session is secure with xlock against other people. If xdm is started in the background (from root, rc.local or something), nobody except root and yourself can kill your xlock. Perhaps a "nohup startx ; logout" would also work. I never tried it.All the best Achim
Achim Neumann Technische Fakultaet, Universitaet Bielefeld Email: achim@TechFak.Uni-Bielefeld.DE