On Tue, Sep 04, 2012 at 01:35:21PM +0200, Johannes Berg wrote: > I would guess that hardware *decryption* is faulty, maybe only one > action frame needs to be correct and so if one of them is nohwcrypt=1 it > still works? Yes, I was assuming that receiving robust unicast management frames would fail with ath5k. This is exactly the reason why I adding IEEE80211_HW_MFP_CAPABLE conditionally in ath9k only for the hardware revisions that support the new CCMP rules. It should be possible to work around this if someone really cares, but that require the driver to re-encrypt the incorrectly decrypted frame (i.e., using the pre-802.11w rules on CCMP exactly in the way the hardware did it) and then pass that end result for masc80211 to decrypt it correctly. I considered doing that for a while, but did not find enough justification to work with that. -- Jouni Malinen PGP id EFC895FA -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
