41–50 of 53 posts
Well, if there's one piece of (somewhat) good news around this and https://www.krackattacks.com/ , it's that TLS and VPNs will become even more common. Where did WEP and WPA2 come from, anyway? What's the historical reason we aren't all using TLS to connect to our APs?
The problem with TLS is that it’s client authentication kinda sucks and isn’t easy to manage.
Earlier quoted context omitted.
I expect they could, yes; WPA2 doesn't offer forward secrecy. But WPA2 never offered much anyway. If you're on mall wifi, you can already see unencrypted traffic for everyone else, because the client keys are derivable from the shared passphrase (which presumably everyone at the mall has been told) and overhearing the four-way handshake when someone joins. And! You can even fake a disconnect message that forces the f…
> * If you're on mall wifi, you can already see unencrypted traffic for everyone else* Without contradicting your observation, I want to mention that virtually anything important you do on the Internet these days--from online banking to Google searches to reading Hacker News--is protected by a second independent layer of encryption: HTTPS. I'm not excusing the WPA2 flaws, but I do think that your bank info, web searc…
Also, HTTPS doesn't protect domain names. If you're making TLS connections to (e.g.) a porn site over WiFi, the other people sharing your connection don't need to decrypt your traffic to know what you're doing.
Earlier quoted context omitted.
WPA2 Enterprise use a central RADIUS server for authentication, with separate credentials for each user, and a (separately-distributed) certificate for the server. It's just not practical for consumer and small-business setups.
Somewhat true. Setting up a Freeradius is not hard. Problem is that you need another device that is running 24/7.
Earlier quoted context omitted.
And on a device equipped with a radio, it's not very hard to generate entropy.
The radio might not be exposed to the OS. If it's a Fullmac device, you usually don't have access to the radio stuff. Even with Softmac, there's not a guarantee.
WPA2 is toast. Ref to the CVEs that will make a lot of network admins hate Monday: https://twitter.com/nick_lowe/status/919527451570638848 And some background: https://eprint.iacr.org/2016/475.pdf
Source: https://www.krackattacks.com/
Earlier quoted context omitted.
The radio might not be exposed to the OS. If it's a Fullmac device, you usually don't have access to the radio stuff. Even with Softmac, there's not a guarantee.
I am sure that's a problem on the client, but on the AP, the manufacturer controls both the hardware and the OS.
Earlier quoted context omitted.
I am sure that's a problem on the client, but on the AP, the manufacturer controls both the hardware and the OS.
Not necessarily. Again with fullmac devices you don't control the complete hardware.
Earlier quoted context omitted.
Spoofed yes but they're hard to guess in advance without prior knowledge of the device's MAC address.
MAC addresses are broadcast in the clear regularly, so any device doing that without some randomization is ripe for the picking.
Earlier quoted context omitted.
Somewhat true. Setting up a Freeradius is not hard. Problem is that you need another device that is running 24/7.
The bit that's less practical for consumer setup is more the cert distribution and setup of separate credentials for each user. (The RADIUS server could even be built into the router in a consumer product.)
Earlier quoted context omitted.
WPA2 in general. The 4-way handshake is vulnerable. Might be patchable, but there is a ton of embedded stuff out there that will never get updated...
I guess the question is whether only the AP needs to be patched or the client as well.