netdev - Re: [PATCH] dnet: Dave DNET ethernet controller driver

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]

Message-Id: <20090311.174446.150354252.davem@davemloft.net>
Date:	Wed, 11 Mar 2009 17:44:46 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	riku.voipio@....fi
Cc:	linux-arm-kernel@...ts.arm.linux.org.uk, netdev@...r.kernel.org
Subject: Re: [PATCH] dnet: Dave DNET ethernet controller driver

From: Riku Voipio <riku.voipio@....fi>
Date: Wed, 11 Mar 2009 21:15:30 +0200

> In such machines, typically the mac address is stored in bootloader's
> configuration area in NOR/NAND flash.

That's a perfectly fine solution as well.

Anything that specifies a unique MAC address somewhere on
the board is OK.

It's this "generate a random MAC address every bootup" that
I am totally against.  A situation where there is no permanent
MAC address stored anywhere.
--
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