You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The attack works for both clients and access points
Updating an access point does not keep clients protected!
However, neither of those statements is strictly true. Access points not implementing 802.11r roaming/FT support (or with it disabled) or client-side features are not affected (they require no patch). This is the majority of residential/home APs, as FT is a feature only used when multiple APs serve the same SSID/network.
Conversely, all access points may implement mitigation for unpatched clients (and, indeed, such mitigation is the only useful thing to be done in an update for APs that do not implement 802.11r). hostapd implements this as the new wpa_disable_eapol_key_retries config option. When that option or equivalent mitigation is enabled, all clients are protected regardless of whether they have been patched or not. Therefore, it would be useful to clarify which vendors are indeed doing this (LEDE is one example, they already have support for this option in the LuCI config file at /etc/default/wireless).
The text was updated successfully, but these errors were encountered:
marcan
changed the title
Access points not always impacted; mitigation available
Access points not always impacted; client mitigation also available
Oct 19, 2017
My suggestion is really that, for most people, not having a firmware update for their home AP is not cause for concern, as it is unlikely to be affected to begin with. AP updates are mostly for high-end/infrastructure APs, and for mitigation of the client-side flaw. So end-users should focus on updating their devices; updating their APs is a good idea but they should not panic if no update is available. Corporate/public WiFi network administrators should be knowledgeable enough to understand the implications and make sure to update their AP fleet.
The info page currently states:
However, neither of those statements is strictly true. Access points not implementing 802.11r roaming/FT support (or with it disabled) or client-side features are not affected (they require no patch). This is the majority of residential/home APs, as FT is a feature only used when multiple APs serve the same SSID/network.
Conversely, all access points may implement mitigation for unpatched clients (and, indeed, such mitigation is the only useful thing to be done in an update for APs that do not implement 802.11r). hostapd implements this as the new
wpa_disable_eapol_key_retries
config option. When that option or equivalent mitigation is enabled, all clients are protected regardless of whether they have been patched or not. Therefore, it would be useful to clarify which vendors are indeed doing this (LEDE is one example, they already have support for this option in the LuCI config file at/etc/default/wireless
).The text was updated successfully, but these errors were encountered: