From owner-freebsd-chat Wed Apr 4 0:33:46 2001 Delivered-To: freebsd-chat@freebsd.org Received: from nsmail.corp.globalstar.com (gibraltar.globalstar.com [207.88.248.142]) by hub.freebsd.org (Postfix) with ESMTP id 5801837B722 for ; Wed, 4 Apr 2001 00:33:44 -0700 (PDT) (envelope-from cjclark@alum.mit.edu) Received: from alum.mit.edu ([207.88.154.6]) by nsmail.corp.globalstar.com (Netscape Messaging Server 4.15) with ESMTP id GB9BNO00.01U; Wed, 4 Apr 2001 00:33:24 -0700 Message-ID: <3ACAEAAF.F7434509@alum.mit.edu> Date: Wed, 04 Apr 2001 02:34:39 -0700 From: "Crist J. Clark" X-Mailer: Mozilla 4.72 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Kris Kirby Cc: Crist Clark , freebsd-chat@FreeBSD.ORG, Peter Radcliffe Subject: Re: su change? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kris Kirby wrote: > > On Tue, 3 Apr 2001, Crist Clark wrote: > > Ummm... This page says, > > > > 7.My Sun is in full-security mode (can't even boot without password) > > and I don't know the EEPROM password. How do I fix this? (Replace chip) > > > > "Replace chip." You know a trick? I'd be curious. I had an admin do > > this once ('course, with our Sun contract, a tech replaced the chip > > the same day, no big deal). > > Smashing ^C like a mad monkey once SunOS starts over the com-console (no > keyboard) is another... > > ^C^C^C^C # > # fsck -p > # mount -a > # eeprom (-flags to change password) > > Then reboot, remove the security (since you now know the password). I > honestly didn't think IPXs would be *that* easy to break into... 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. However, that method would be relevant to the start of this thread, how to get access when /etc/passwd is munged. -- Crist J. Clark cjclark@alum.mit.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message