Article View: comp.security.misc
Article #333Re: Locking terminals (was Re: New Princeton Policy)
From: Fergus James HENDERSON
Date: Fri, 11 Sep 1992 08:28
Date: Fri, 11 Sep 1992 08:28
47 lines
2685 bytes
2685 bytes
S_TITZ@iravcl.ira.uka.de (Olaf Titz) writes: >> In article <CKD.92Sep9143724@loiosh.eff.org>, ckd@eff.org (Christopher Davis) writes: >> |> Olaf> This means: 'If you must go to the restroom you HAVE to leave the >> |> Olaf> terminal open, so that other users can terminate your session if >> |> Olaf> they need the machine.' This is IMO simply unacceptable. Other >> |> Olaf> policies would REQUIRE to lock the terminal to prevent tampering >> |> Olaf> with your account. >> |> >> |> MIT's Athena workstation policy is that you can lock it for no more than >> |> 20 minutes before someone can feel free to reboot it or otherwise >> |> "forcibly unlock" it. The "standard" screenlocker has a displayed timer > >Rebooting is not the way of choice, I think... > >> |> of "how long I've been locked". >> |> >>... >> At Rice, we have an X windows lockscreen program with a twenty minute >> timer. After twenty minutes, the lockscreen itself logs the user out. >> The logout is pretty clean. The only thing we haven't solved yet is >> how to get the user's .logout file to be read on logout by the >> lockscreen program. > >What about the following? > >A locking program that >- displays the time it is running, >- after N minutes provides a button which will log the user out (with >N preferrably to be specified in a configuration file), >- perhaps communicates with other workstations in the cluster, to >enable the logout only when no other workstation is idle. > >I leave the gory details of the implementation to the people who know >X (that excludes me, unfortunately ;-) Here at Melbourne Uni on one of the student machines, the lock command has a default time-out of 15 minutes. After 15 minutes, lock terminates and drops back into your shell, leaving your account wide open. -- Fergus Henderson fjh@munta.cs.mu.OZ.AU This .signature virus is a self-referential statement that is true - but you will only be able to consistently believe it if you copy it to your own .signature file!
Technical Details
Message-ID:
<9225518.22142@mulga.cs.mu.OZ.AU>Path:
arc1-ca.pugleaf.net!sparky!uunet!munnari.oz.au!cs.mu.OZ.AU!munta.cs.mu.OZ.AU!fjhReferences:
<1992Sep8.193517.12597@eff.org> <1992Sep9.094246.819@rz.uni-karlsruhe.de> <CKD.92Sep9143724@loiosh.eff.org> <BuBxzz.A21@rice.edu> <1992Sep10.161835.20380@rz.uni-karlsruhe.de>Show Full Headers
Complete Article Headers
Newsgroups: comp.security.misc Path: arc1-ca.pugleaf.net!sparky!uunet!munnari.oz.au!cs.mu.OZ.AU!munta.cs.mu.OZ.AU!fjh From: fjh@munta.cs.mu.OZ.AU (Fergus James HENDERSON) Subject: Re: Locking terminals (was Re: New Princeton Policy) Message-ID: <9225518.22142@mulga.cs.mu.OZ.AU> Sender: news@cs.mu.OZ.AU Organization: Computer Science, University of Melbourne, Australia References: <1992Sep8.193517.12597@eff.org> <1992Sep9.094246.819@rz.uni-karlsruhe.de> <CKD.92Sep9143724@loiosh.eff.org> <BuBxzz.A21@rice.edu> <1992Sep10.161835.20380@rz.uni-karlsruhe.de> Date: Fri, 11 Sep 1992 08:28:37 GMT Lines: 47