*BSD News Article 79881


Return to BSD News archive

Newsgroups: comp.unix.bsd.bsdi.misc,info.bsdi.users,mvis.lists.bsdi-users
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!nntp.coast.net!news.kei.com!news.mathworks.com!newsgate.duke.edu!news.eff.org!sed.psrw.com!news.apk.net!wariat.org!news.nask.pl!news.icmp.lviv.ua!news.freenet.kiev.ua!news.isf.kiev.ua!news.free.net!news.phys.msu.su!news.rssi.ru!demos!satisfy.kiae.su!news.simtel.ru!--techno.ru--:ExServ_V05.01.08
From: colinj@math.math.unm.edu (Colin Eric Johnson)
Subject: Making booting secure
Date: Tue,  1 Oct 96 03:02:18 +0400
Message-ID: <52peqv$85h@lynx.unm.edu>
Reply-To: "Colin E. Johnson" <colinj@unm.edu>
Organization: University of New Mexico, Albuquerque
Distribution: world
NNTP-Posting-Host: simtel.ru
Sender: news-server@simtel.ru (ExServ V05.01.08)
Approved: bsdi-users@mvc.net
X-Return-Path: <devnull@techno.ru>
X-CRC-ID: :5e617a58:afbd7bc3:28a58741:
Lines: 14
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.bsdi.misc:5052 info.bsdi.users:9199

I'm upgrading about 30 machines to 2.1 and I need to make the boot
process as secure as possible. They all sit in a "public" lab so any
user who saw fit could power one off, restart the machine and then
interrupt the init process to get a single user shell. 

I'm looking for a way to make the entire process secure so this cannot
happen. Either I would like init (and the rc scripts) to reboot the
machine if the process is interrupted or I would like to force the
user to enter some kind of password. 

Does anyone have any suggestions?
-- 
"Now my life is better than an ABBA song" - Muriel, "Muriel's Wedding"
Colin E. Johnson | colinj@unm.edu | http://www.unm.edu/~colinj/