netdev - Re: WiFi and changed MAC addrs

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] [day] [month] [year] [list]

Message-Id: <1189006484.9942.113.camel@johannes.berg>
Date:	Wed, 05 Sep 2007 17:34:44 +0200
From:	Johannes Berg <johannes@...solutions.net>
To:	Ben Woodard <woodard@...hat.com>
Cc:	netdev@...r.kernel.org
Subject: Re: WiFi and changed MAC addrs

On Wed, 2007-09-05 at 08:20 -0700, Ben Woodard wrote:

> If a particular piece of hardware will refuse to send frames after the 
> MAC address has been changed, then shouldn't the card's driver refuse to 
> allow a change of the MAC address and return an error in response to the 
> IOCTL that tries to change it?

Yes.

> I can't think of a situation where this 
> wouldn't be the right thing to do. However, before I submit a patch to 
> fix this, does anyone else know of any special cases that I might need 
> to deal with?

That wouldn't make sense now, would it?

> Also is behavior of refusing to send frames with a non-hardware 
> specified MAC address part of the WiFi spec or is it particular to 
> certain WiFi cards? IOW at what level do I need to fix it? Should I just 
> fix it for the Intel cards that I've tested or do I need to fix it for 
> all WiFi cards?

Most wifi cards don't care at all what MAC address you send, in fact
allowing you to send with various MAC addresses. So this is something
intel specific. Oh are we talking about iwlwifi? If so, please report to
their maintainers immediately, they're lazy bastards and don't even
upload the new MAC address to the card even if they could.

johannes

Download attachment "signature.asc" of type "application/pgp-signature" (191 bytes)