From owner-freebsd-hackers Tue Jan 3 20:07:33 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id UAA14284 for hackers-outgoing; Tue, 3 Jan 1995 20:07:33 -0800 Received: from bsd.coe.montana.edu (bsd.coe.montana.edu [153.90.192.4]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id UAA14278 for ; Tue, 3 Jan 1995 20:07:32 -0800 Received: (nate@localhost) by bsd.coe.montana.edu (8.6.8/8.3) id VAA06449; Tue, 3 Jan 1995 21:11:41 -0700 Date: Tue, 3 Jan 1995 21:11:41 -0700 From: Nate Williams Message-Id: <199501040411.VAA06449@bsd.coe.montana.edu> In-Reply-To: John Utz "FreeBSD on SCHOOL SYSTEMS????" (Jan 3, 5:43pm) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: John Utz , FreeBSD hackerlist Subject: Re: FreeBSD on SCHOOL SYSTEMS???? Sender: hackers-owner@FreeBSD.org Precedence: bulk > I would like to here from all people sysadmining a collection of > student pc's running freebsd > > How do you keep folks from sticking a boot disk in; logging in as > root, and spamming the whole system? Most students don't have the ability to build a boot disk, and those that do probably won't. But, if you are worried, you can put a password on the BIOS on the computer and disable booting from floppy. And, if you are *really* concerned you can disable the wait on the bootblocks to keep them from going single user or at least make the console insecure which forces them to enter a password. Nate