https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213621
--- Comment #12 from Adrian Chadd <adr...@freebsd.org> --- Hiya, So the beacon miss / TSFOOR is the driver side. I can go take another look at fixing that up. The CCMP replay attack thing - that we need another NIC to sniff the air in monitor mode and try to capture the invalid PN showing up in the air. If it's coming over the air then sure, we can nail it down. If it's not coming over the air, and instead it's corrupted by the AR9380 NIC, we're in trouble. I need to go double / triple-check to see if we pass frames that fail CRC/FCS/decrypt up to the stack for incorrect processing. I'm kinda worried that we're processing invalid frames a little too far along the input / decryption path. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
