From owner-freebsd-chat Wed Apr 4 9: 2:17 2001 Delivered-To: freebsd-chat@freebsd.org Received: from Spaz.HuntsvilleAL.COM (spaz.huntsvilleal.com [63.147.8.31]) by hub.freebsd.org (Postfix) with ESMTP id 6F3D637B722 for ; Wed, 4 Apr 2001 09:02:04 -0700 (PDT) (envelope-from kris@catonic.net) Received: from localhost (kris@localhost) by Spaz.HuntsvilleAL.COM (8.9.3/8.9.3) with ESMTP id QAA12559; Wed, 4 Apr 2001 16:01:40 GMT (envelope-from kris@catonic.net) Date: Wed, 4 Apr 2001 16:01:39 +0000 (GMT) From: Kris Kirby X-Sender: kris@spaz.huntsvilleal.com To: "Crist J. Clark" Cc: freebsd-chat@FreeBSD.ORG, Peter Radcliffe Subject: Re: su change? In-Reply-To: <3ACAEAAF.F7434509@alum.mit.edu> Message-ID: X-Tech-Support-Email: bofh@catonic.net MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 4 Apr 2001, Crist J. Clark wrote: > That's in full-security mode? In full-security mode, the machine will > not go past the boot prompt without a password. It will not start > going into multi-user mode; the OS never will start to boot. Negative; that's just if it's in "lab" mode. Like a BIOS password... > However, that method would be relevant to the start of this thread, > how to get access when /etc/passwd is munged. Nifty, I guess. ----- Kris Kirby, KE4AHR | TGIFreeBSD... 'Nuff said. | ------------------------------------------------------- "Fate, it seems, is not without a sense of irony." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message