Quote:
Originally Posted by Jon Jack
The issue isn't just trying to connect to the network, the issue is trying to connect to the network - while entering an incorrect WPA key
|
Keep in mind that no key == an incorrect key, although I don't know if that applies in this specific attack. If it does, though, it increases the likeliness of it happening accidentally greatly.
Also note that it seems only some versions of the AP firmware have the bug, so this is not a long-standing issue.
Quote:
Originally Posted by Joe Johnson
Fifth, it seems to me that FIRST (and the FMS) has one implied contract with the teams: We will get X% of your data packets from your Operator Interface to your Robot and vice versa within Y msec.
|
AFAIK, this is basically what QoS is for, and the way they've described it in the report, it seems they're not using it yet (but will be next year).
As a side note, I'm also in the "stupidity rather than malice" camp, but from the looks of it, it wasn't just one person responsible. Either way, the actions taken were appropriate IMO -- including the provided anonymity.