netdev - Re: [PATCH] dm9601: handle corrupt mac address

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:	Tue, 6 Jan 2009 02:28:16 -0800
From:	David Brownell <david-b@...bell.net>
To:	Peter Korsgaard <jacmet@...site.dk>
Cc:	Wu Fengguang <wfg@...ux.intel.com>, netdev@...r.kernel.org
Subject: Re: [PATCH] dm9601: handle corrupt mac address

On Tuesday 06 January 2009, Peter Korsgaard wrote:
> So what happens if you plug in 2 devices without an EEPROM? Do they
> get the same MAC address? That seems broken.

What happens when you unplug one then re-plug it?  Maybe
someone trips over the USB cable, or it gets an electrical
glitch that evalutes to disconnect/reconnect... It gets
the same address again.  Not particularly broken.

Note that Ethernet was *designed* around using a single
address per host ... I still have XNS docs sitting around
somewhere, that was a fairly significant thing.  One of the
original reasons Ethernet adapter addresses could change
was to make sure that all Ethernet interfaces on a host
would use the same address.

That said ... if it bothers you, that's easy to change
in userspace.  This code has worked this way for around
nine years now; I don't recall any previous complaints.

- Dave

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html