On Thu, 25 Aug 2005 20:30:26 -0400, Jeff Garzik wrote: > > add-seq-number.patch > > Adds sequence numbers to transmitted frames. > > any security implications here, as with TCP sequence numbers?
802.11 sequence numbers are intended solely for duplicate frame filtering (chapter 9.2.9 in IEEE 802.11 specification). The only security risk I can imagine is that somebody will send fake frame with stolen MAC address and with sequence number that is expected to be sent by owner of that MAC address soon. This will lead to DoS only, as the fake frame will be dropped (we are not concerned with unencrypted connection of course). And it is so easy to perform DoS attack to wifi in bazillion ways that this really doesn't matter. > Can any of these patches be moved above the ieee80211_device patch? IMO it doesn't make much sense to pass net_device to most functions just to let them find the address of ieee80211_device as the first step they have to do. Thanks, -- Jiri Benc SUSE Labs - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html