fragattacks

mirror of https://github.com/vanhoefm/fragattacks.git synced 2025-02-26 13:49:35 -05:00

History

Jouni Malinen afa2ffb413 SAE: Check Status Code in Authentication frames

While other authentication algorithms mark Status Code as being Reserved
in the case of the transaction number 1, SAE does not. Check that the
Status Code indicates success before creating SAE state. In addition,
fix the mesh anti-clogging token request parsing on big endian CPUs.

Transaction number 2 (confirm) can also have non-zero Status Code to
report an error. Those should be processed, but not replied to with yet
another error message. This could happen in mesh case. Avoid a loop of
error messages by dropping the non-success case without additional
response.

In addition, don't reply to unknown transaction numbers if the status
code is non-zero. This avoids a loop of error messages if an invalid
frame where to be injected (or unlikely corruption were to occur).

Signed-off-by: Jouni Malinen <j@w1.fi>

2014-12-15 00:06:56 +02:00

SAE: Check Status Code in Authentication frames

2014-12-15 00:06:56 +02:00

common

Clean up VHT configuration validation

2014-12-14 19:00:38 +02:00

crypto

OpenSSL: Simplify EAP-FAST peer workaround

2014-12-09 23:55:41 +02:00

drivers

mesh: Add mesh interface creation command for mesh gate

2014-12-14 23:27:43 +02:00