Article View: comp.security.misc
Article #353Re: Locking terminals (was Re: New Princeton Policy)
From: Amos Shapira
Date: Sun, 13 Sep 1992 08:03
Date: Sun, 13 Sep 1992 08:03
21 lines
1385 bytes
1385 bytes
ckd@eff.org (Christopher Davis) writes: >Simple policy fix: ``If the terminal is locked with anything other than >the "standard" lockscreen, it may be rebooted in order to clear the >lock.'' And what will prevent users from hacking a lock programme which looks just like the real thing, only without its restrictions? And, on the other side, what will prevent users who want a locked terminal from rebooting it and saying it looked like it wasn't locked by the right programme? From meny discussions like this I got to the general desparing conclusion that the best way to deal with such problems is to educate the users to be honest, now how do you do that? Cheers, -- --Amos Shapira (Jumper Extraordinaire) C.S. System Group, Hebrew University, Jerusalem, Israel amoss@cs.huji.ac.il
Technical Details
Message-ID:
<amoss.716371405@shuldig>Path:
arc1-ca.pugleaf.net!sparky!uunet!elroy.jpl.nasa.gov!usc!sol.ctr.columbia.edu!zaphod.mps.ohio-state.edu!rpi!bu.edu!wang!newsReferences:
<CKD.92Sep9143724@loiosh.eff.org> <BuBxzz.A21@rice.edu> <1992Sep10.161835.20380@rz.uni-karlsruhe.de> <68006@hydra.gatech.EDU> <CKD.92Sep11153929@loiosh.eff.org>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!elroy.jpl.nasa.gov!usc!sol.ctr.columbia.edu!zaphod.mps.ohio-state.edu!rpi!bu.edu!wang!news From: amoss@huji.ac.il (Amos Shapira) Newsgroups: comp.security.misc Subject: Re: Locking terminals (was Re: New Princeton Policy) Message-ID: <amoss.716371405@shuldig> Date: 13 Sep 92 08:03:25 GMT References: <CKD.92Sep9143724@loiosh.eff.org> <BuBxzz.A21@rice.edu> <1992Sep10.161835.20380@rz.uni-karlsruhe.de> <68006@hydra.gatech.EDU> <CKD.92Sep11153929@loiosh.eff.org> Sender: news@wang.com Organization: Mail to News Gateway at Wang Labs Lines: 21