home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!rutgers!njitgw.njit.edu!hertz.njit.edu!dic5340
- From: dic5340@hertz.njit.edu (David Charlap)
- Newsgroups: comp.os.os2.apps
- Subject: Re: Locking OS/2 on boot (passwd protection)
- Message-ID: <1992Aug27.183247.9699@njitgw.njit.edu>
- Date: 27 Aug 92 18:32:47 GMT
- References: <BtnA98.30@news.cso.uiuc.edu>
- Sender: news@njit.edu
- Organization: New Jersey Institute of Technology, Newark, N.J.
- Lines: 27
- Nntp-Posting-Host: hertz.njit.edu
-
- In article <BtnA98.30@news.cso.uiuc.edu> btf57346@uxa.cso.uiuc.edu (Byron "Bohr" Faber) writes:
- >Ok. I like os/2's password protection, but does anybody have an idea
- >how to get it to lock up on boot. It doesn't do me much good if it
- >will only look up after 3 minutes idle, or if I tell it to.
-
- !!!!! The original Lockup program (shipped with OS/2 1.3, CSD level
- WR5016) locked up immediately after boot. Users complained bitterly
- that the had to type a password to enter their systems in the morning,
- so IBM removed that "feature" from the next CSD release (WR 5050).
-
- Perhaps this should have been moved to a configuration option.
-
- The 1.3 users were probably PS/2 users. PS/2's have a power-on
- password stored in the CMOS, making such a "feature" redundant and
- annoying.
-
- It also bothers me that Lockup prevents CTRL-ALT-DEL from rebooting.
- This doesn't increase security any, since I can just power off and on
- to get back in, and then there's the chance that the disk would be
- messed up. If I want to prevent CTRL-ALT-DEL, I can just lock the
- keyboard with that key switch on the front of the computer or assign a
- power-on password, if it's a PS/2.
- --
- |) David Charlap "I don't even represent myself
- /|_ dic5340@hertz.njit.edu sometimes so NJIT is right out!.
- ((|,)
- ~|~ Hi! I am a .signature virus, copy me into your .signature file.
-