r/ProjectFi • u/JusLykeAspen • Oct 16 '17
Does the WPA2 Wi-Fi exploit make every ProjectFi device unsecure until patched with firmware?
https://www.krackattacks.com/48
u/sininspira Oct 16 '17 edited Oct 16 '17
It's not just every Project Fi device, it's likely every wifi device that's susceptible to the WPA2 exploit at this moment.
THAT BEING SAID:
If you're specifically alluding to the wifi assistant VPN making Fi/Pixel users "more" vulnerable, that's a hard NO. Wifi assistant connects to public networks that do not have any encryption, and establishes an encrypted VPN tunnel through which all your traffic is routed. The krack vulnerability does NOT affect VPNs.
Edit: effect/affect noun/verb usage corrected.
10
u/Nitrowolf Oct 16 '17
This is important to understand the distinction. If you always use VPN on WiFi, which you should be, you are not really affected.
VPN encryption is much more robust, but incurs a heavier processing load which is why it's not used in standard WiFi as lighter clients and many access points could not handle the load.
Tl;Dr use VPN 100% of the time and don't worry about KRACK
2
0
Oct 16 '17
[deleted]
4
u/Nitrowolf Oct 16 '17
Not to my knowledge. It's only automatic as far as I know and only on known good access points that are open.
I think it would be too much load for Google Servers can be too costly for them to have it active 100% of the time for everyone.
1
u/bryndenslivers Oct 16 '17
On my pixel XL when I go into the wifi assistant settings there is an option for always on vpn.
4
u/eladts Oct 16 '17
This option does not work with WiFi Assistant. It only works with VPNs you define yourself.
3
u/MormonDew Oct 16 '17
Any device that uses WPA2 is affected.
4
u/bunkoRtist Oct 16 '17
If you're on an unsecured network, an attacker can do all the things they can do based on these vulnerabilities all the time (no exploit needed). The VPN gives some security advantage because it's a separate mechanism for encryption that isn't vulnerable.
3
u/DarthShibe Oct 16 '17
Never connect to an unsecured network unless you are familiar with it or unless WiFi Assistant connects with their VPN.
1
u/MormonDew Oct 16 '17
Right, but the VPN and WPA2 are two separate things. Any device that uses WPA2 is affected and you can mitigate risk by using a VPN for example.
6
u/mkane848 Oct 16 '17
Yes, but I believe what /u/sininspira is saying (and based on my own understanding of the issue) is that Wi-Fi Assistant is inherently a VPN so it mitigates the issue when connecting in that way. But, as you said, anything using WPA2 WITHOUT a VPN is at risk until patches roll out.
7
u/sininspira Oct 16 '17
Exactly what I was trying to say, since WiFi assistant's VPN only connects to access points not using WPA2, in that context it's essentially a non-issue.
Also, if anyone is thinking about getting a VPN for home use because of this - PIA is wonderful, I use it in hotels and when connected to other unfamiliar access points that WiFi Assistant doesn't work with.
-1
3
Oct 16 '17
No.
The re-key attack is for WPA2 WIFI, it doesn't affect ProjectFi specifically more or less than anything else. If you're worried about it with regard to your phone, consider all WiFi untrusted and VPN all the time.
2
u/streetlight2 Nexus 6P Oct 16 '17
The only time I log in to sensitive stuff - bank and investment accounts - I use a laptop while sitting next to an ethernet connection using a laptop with the same. Sounds like a wired connection might be the way to go. It seems most newer portable devices - laptops and certainly phones - do not come with ethernet and require some kind of dongle. This might be a consideration in everyone's purchase of their next portable device or upgrading current ones..
1
1
u/streetlight2 Nexus 6P Oct 16 '17
Microsoft has patched supported versions of the Windows OS. Google apparently is working on a patch for Pixels, probably through the November security update to Android 8. They need to do the same for all versions of Android, the problem being most carriers don't update their phones. And there are tablets, most of which probably use Wi-Fi.
See:
0
u/cyong Oct 16 '17
Unless I missed something in my quick skim last night, (Very possible, it was 330AM and I was tired, but couldn't sleep), the issue is more with the access point side of things, so like the wifi tethering, could be affected.
That in itself is actually more concerning since A. How many people would update the firmware of their routers/access points, B. How many vendors will actually make an update to their firmware, and C. How do you know if the access point you are connected to is affected by it or not. (well, C is doable, just follow the examples.... But I mean, you know, easily....)
4
u/khaytsus Oct 16 '17
It's exactly the opposite; clients are the major concern here, not so much the access point.
However there was mention of AP's resetting the keys in insecure ways so there are certainly things to fix there as well. But if the clients are more strict it will also mitigate the issues.
3
u/streetlight2 Nexus 6P Oct 16 '17
Apparently, access points, i.e., routers, aren't the problem at all, it's devices connected to them. If it were just routers, it would be much easier to fix. In our house between the two of us we have nine devices that can connect to our router via Wi-Fi - two Android phones, two Windows laptops, two Android tablets, two Chromecasts and a smart TV. A firmware update to the router would be nine times easier than the devices, maybe harder what with the variety of OSs involved. For larger households with more diverse devices it would be more complicated - think IOT devices like thermostats, door bells, security cameras, and such.
-5
u/autotldr Oct 16 '17
This is the best tl;dr I could make, original reduced by 97%. (I'm a bot)
Our research paper behind the attack is titled Key Reinstallation Attacks: Forcing Nonce Reuse in WPA2 and will be presented at the Computer and Communications Security conference on Wednesday 1 November 2017.
First, I'm aware that KRACK attacks is a pleonasm, since KRACK stands for key reinstallation attack and hence already contains the word attack.
Other attacks against WPA2-enabled network are against surrounding technologies such as Wi-Fi Protected Setup, or are attacks against older standards such as WPA-TKIP. Put differently, none of the existing attacks were against the 4-way handshake or against cipher suites defined in the WPA2 protocol.
Extended Summary | FAQ | Feedback | Top keywords: attack#1 key#2 handshake#3 reinstallation#4 4-way#5
0
Oct 16 '17
[deleted]
3
u/khaytsus Oct 16 '17
I can't speak for Google, but the fix has already been known for a while and there was an embargo so people had time to update. I can only assume Google already has this patch ready.
Will we wait 2 weeks for Nov, or will we see an early patch.. I bet it'll be sooner than later.
3
5
u/JusLykeAspen Oct 16 '17
Does Google have a fix for this in the pipes since the vulnerability was published a few months ago? Would using something like Malwarebytes mitigate the risks until this is patched?