Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Access points not always impacted; client mitigation also available #133

Open
marcan opened this issue Oct 19, 2017 · 2 comments
Open

Access points not always impacted; client mitigation also available #133

marcan opened this issue Oct 19, 2017 · 2 comments

Comments

@marcan
Copy link

marcan commented Oct 19, 2017

The info page currently states:

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).

@marcan marcan changed the title Access points not always impacted; mitigation available Access points not always impacted; client mitigation also available Oct 19, 2017
@kristate
Copy link
Owner

This is intentionally kept simple -- the attack does work on access points (albeit not all APs)

Ultimately it is important for customers to check with their vendor / this list if their are affected.

Remember: most people are not of technical nature -- wifi is used by everyone.

I will keep this thread open for the time being to collect comments -- thanks!

@marcan
Copy link
Author

marcan commented Oct 20, 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants