From owner-freebsd-questions Wed Feb 11 14:07:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA00573 for questions-outgoing; Wed, 11 Feb 1998 14:07:57 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from scifair.acadiau.ca (scifair.acadiau.ca [131.162.8.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA00533 for ; Wed, 11 Feb 1998 14:07:17 -0800 (PST) (envelope-from miker@scifair.acadiau.ca) Received: (from miker@localhost) by scifair.acadiau.ca (8.8.5/8.8.5) id SAA24704; Wed, 11 Feb 1998 18:06:48 -0400 (AST) From: Michael Richards Message-Id: <199802112206.SAA24704@scifair.acadiau.ca> Subject: Re: Security In-Reply-To: from Steve Hovey at "Feb 11, 98 02:55:10 pm" To: shovey@buffnet.net, freebsd-questions@FreeBSD.ORG Date: Wed, 11 Feb 1998 18:06:48 -0400 (AST) Reply-To: 026809r@dragon.acadiau.ca X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Is FreeBSD C2 security standards compliant ?? If so, what version did > > these security features debut ?? > > No it is not - I believe to be C2 you must not be able to gain access to > the disks even from the console of the machine itself without a valid > userid and password - and with FreeBSD you can boot with -s to bring it up > standalone as root. If this is the only thing FreeBSD needs to be C2 compliant, maybe someone could come up with some kind of fix where your username and password can optionally be put in the boot block so you need it to give any startup options on bootup. Then use the bios to stop flopy bootups. Would that satisfy the requirements? -mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe questions" in the body of the message