3 ms·
Pray for a vendor patch. The fix landed today in the hostap repository: https://w1.fi/cgit/hostap/commit/?id=a00e946c1c9a1f9cc65c72900d2a444ceb1f872e https://w
by Tepix 9y ago
Pray for a vendor patch. The fix landed today in the hostap repository:
https://w1.fi/cgit/hostap/commit/?id=a00e946c1c9a1f9cc65c72900d2a444ceb1f872e https://w1.fi/cgit/hostap/commit/?id=a00e946c1c9a1f9cc65c729...
- rightos 9y agoDoes this resolve the issue on the AP side of things? Could I theoretically have an AP update that would resolve this with no need to update clients?
- tesseract 9y agoUnfortunately no, from what I understand this is primarily an attack against clients.
- rightos 9y agoAh yes, I see now that the patch is actually to wpa_supplicant. Well, hopefully this means no kernel patch will be needed.
- pritambaral 9y agoBoth APs and clients need to be patched[0]. Mitigations are possible on AP side if no updates are available[1]. [0]: "Finally, although an unpatched client can still connect to a patched AP, and vice versa, both the client and AP must be patched to defend against all attacks!" [1]: "you can try to mitigate attacks against routers and access points by disabling client functionality (which is for example used in repeater modes) and disabling 802.11r (fast roaming)."