linux-kernel - Re: forcedeth net driver: reverse mac address after pxe boot

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: <20061005144442.GB18408@tuxdriver.com>
Date:	Thu, 5 Oct 2006 10:44:50 -0400
From:	"John W. Linville" <linville@...driver.com>
To:	Alex Owen <r.alex.owen@...il.com>
Cc:	linux-kernel@...r.kernel.org, c-d.hailfinger.kernel.2004@....net,
	aabdulla@...dia.com
Subject: Re: forcedeth net driver: reverse mac address after pxe boot

On Wed, Oct 04, 2006 at 05:19:20PM +0100, Alex Owen wrote:

> The obvious fix for this is to try and read the MAC address from the
> canonical location... ie where is the source of the address writen
> into the controlers registers at power on? But do we know where that
> may be?

This seems like The Right Thing (TM) to me, but we need someone from
NVidia(?) to provide that information.  Ayaz?

> The other solution would be unconditionally reset the controler to
> it's power on state then use the current logic? can we reset the
> controller via software?

This seems like a plausible alternative.

The MAC address validation schemes suggested by others would probably
"work", but they would be a bit fragile.  For example, every new vendor
of forcedeth hardware would have a new OUI to be added to the list.

John
-- 
John W. Linville
linville@...driver.com
-
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/