From owner-freebsd-chat Tue Apr 3 19:36: 4 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 2A4C737B728 for ; Tue, 3 Apr 2001 19:35:47 -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 CAA94807; Wed, 4 Apr 2001 02:35:43 GMT (envelope-from kris@catonic.net) Date: Wed, 4 Apr 2001 02:35:43 +0000 (GMT) From: Kris Kirby X-Sender: kris@spaz.huntsvilleal.com To: Crist Clark Cc: freebsd-chat@FreeBSD.ORG, Peter Radcliffe Subject: Re: su change? In-Reply-To: <3ACA2471.A5AF44AD@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 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... ----- 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