3 ms·

I can't quite see how this can be a spec bug... I mean, why would client A be able to change the key used for communicating with client B? Does this rely on s

I can't quite see how this can be a spec bug... I mean, why would client A be able to change the key used for communicating with client B? Does this rely on some kind of confusion between clients? ie. force a client to disconnect, then the attacker connects using its mac address, and receives all the queued frames?

Retr0id 3y ago
They use the words "lack of explicit guidance", so maybe more of an unspecced-bug rather than a spec bug - but it's the same thing at the end of the day.
- upofadown 3y ago
  Saying that the spec should contain more guidance implies that that guidance is relatively obvious. It also implies that there is one correct way to resolve the issue that the guidance would resolve. That might not be the case. So it is usually best not to claim a specification issue where none technically exists. Just state clearly what you think should be done and leave it at that. The specification might not be incomplete depending on what approach is eventually taken.