linux-kernel - Re: Intel 82559 NIC corrupted EEPROM

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 3 Nov 2006 22:28:08 -0800
From:	thockin@...kin.org
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	John <me@...vacy.net>, linux-kernel@...r.kernel.org,
	linux.nics@...el.com
Subject: Re: Intel 82559 NIC corrupted EEPROM

On Fri, Nov 03, 2006 at 10:22:51PM -0800, thockin@...kin.org wrote:
> On Fri, Nov 03, 2006 at 05:46:25PM -0800, H. Peter Anvin wrote:
> > Basically, Auke wants you to throw away your NIC and/or motherboard. 
> > Since you're effectively dead, the only damage you can do by disabling 
> > the check has already been done.  This unfortunately seems to be fairly 
> > common with e100, especially for the on-motherboard version, and you 
> > basically have two options: either disable the check or write an offline 
> > tool to reprogram the EEPROM.
> 
> I have a tool to write the eepro100 EEPROM.  Let me see if I can find it.
> It even had all the default data coded, ready to restore a NIC to default.
> 
> However - back in the eepro100.c days, it was considered a warning only if
> the EEPROM had a bad checksum.  There were two "supported" formats for the
> EEPROM, one of which was just the MAC address.  And it worked!

One from the vaults:  http://www.hockin.org/~thockin/enet_eeprom/

It's pretty simple, but easily hacked.  ifdown your interface first! :)

Tim
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/