linux-kernel - Re: forcedeth

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: <20060928020438.GC3521@atjola.homenet>
Date:	Thu, 28 Sep 2006 04:04:38 +0200
From:	Björn Steinbrink <B.Steinbrink@....de>
To:	Andrew Morton <akpm@...l.org>
Cc:	Martin Filip <bugtraq@...ula.net>, linux-kernel@...r.kernel.org,
	Ayaz Abdulla <aabdulla@...dia.com>
Subject: Re: forcedeth - WOL [SOLVED]

On 2006.09.27 18:36:25 -0700, Andrew Morton wrote:
> On Thu, 28 Sep 2006 03:01:33 +0200
> Björn Steinbrink <B.Steinbrink@....de> wrote:
> 
> > > > > Do we know if this reversal *always* happens with this driver, or only
> > > > > sometimes?
> > 
> > I only tried 2.6.18 twice this time, but when I wrote my own tool to do
> > it, I had probably 20-30 power on -> ethtool -> poweroff cycles before I
> > decided to look into Bugzilla. As it looked like being fixed already and
> > I did use the nForce NIC for testing only, I didn't spend any further
> > time on it back then.
> 
> What I'm angling towards is: "is this just a driver bug"?

I just took a peek at the code.

The version on bugzilla (last attachment, comment #22), which was
reported to work correctly, has the MAC address reversal hardcoded.
The driver in 2.6.18 has some logic to detect if it should reverse the
MAC address. So it looks like a hardware oddity/bug that the driver
wants to fix but fails. I'll see what happens if I force address
reversal and if I can decipher anything, but probably someone else will
have to cast the runes...

Björn
-
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/