What does the “KEY” mean?
First off, the “key” simply means that Project Fi’s WiFi Assistant is using an open WiFi hotspot to route all of your data through a Google VPN (see diagrams 2 and 4 below). What this means to you is that your data is encrypted from your phone all the way to Google’s VPN server.
While we don’t know all of the rules for when Google’s WiFi Assistant will automatically connect, we do know that (at current) it only works on open hotspots with no “captive portal”. What does that mean? It means that if you have to provide a passphrase (WEP / WPA2 password for the router) or you have to acknowledge a Terms Of Service or click through a “Welcome” page (captive portal), WiFi Assistant won’t automatically connect and the vpn won’t be used.
Beyond that, we’ve been told that hotspot owners can “opt out” of providing this service and that Project Fi uses “a network quality database to help determine which networks are high quality and reliable.” I’ve also seen the WiFi Assistant connect in a location one day but then not the next day – general consensus is that the location may or may not be “WiFI Assistant” material on a given visit based on connectivity at that time.
Why do you call it a “KEY” and how do I know if I get one?
I’ve got a “KEY”, why do I care?
Well, the primary reason is that the key means that your data is encrypted from your phone to Google. In the diagram below, this means that you don’t have to worry about “points of attack” A through E below.
Secure Data Transfer
What are the likely points of attack?
- A – between your phone and the WiFi hotspot. This is the easiest point of attack because the attacker doesn’t need physical access to any of the network hardware. He can simply “listen to” (sniff) your WiFi radio connection. Also keep in mind that some WiFi encryption protocols have been successfully hacked – for instance WEP is basically useless. Just because the hotspot you are connected to uses WEP or WPA2 doesn’t mean it can’t be sniffed.
- B – at the “hotspot”. Hotspots are basically computers. It’s quite possible to embed malicious code in a hotspot to compromise data. This is reportedly common at some “cyber cafes” and other “public” hotspots.
- C – between the hotspot and the ISP. This isn’t very likely because it would require physically tapping the connection (think Police / NSA).
- D – at the hotspot’s ISP. Remember that while you trust your ISP, not all hotspot owners are using trustworthy upstream providers. A small provider with a rogue employee has access to 100% of the the unencrypted traffic going through their servers.
- E – between the ISP and the “internet”. Ok, this is kind of the same thing as G below, but I mention it specifically because it is one of the hack points the NSA has used to log traffic going into / out of the backbone.
- F – the internet. When you connect to a web site, you don’t connect “directly” to that site. Your data bounces from server to server (sometimes 10-20 “hops”) before getting to the other end. If your data isn’t encrypted, it can be compromised at any of these hops.
- G – between the internet and the web server. This would usually be used to see who is using a specific web server. Police would use this to log users connecting to illicit servers and hackers would target this to get “high value” data going to a specific server.
Possible Connection Scenarios
I’m going to arbitrarily assign weights to each of the 7 points of attack above (based on my opinion how likely each is).
A=4, B=2, C=0.5, D=1.5, E=0.5, F=1, G=0.5
So, if you are still with me (I’m surprised I haven’t bored you to death), let’s look at the 6 scenarios above and security rating (based on the scale above 0-10 with higher being better):
- Using an open WiFi Hotspot with HTTP protocol. In this case, your data can be captured at any point (A-G). Rating: 0
- Using an open WiFi Hotspot with HTTP protocol and a “KEY” (Google VPN). In this case, you are protected from your phone to Google. This will defeat the vast majority of sniffing attempts. Rating: 7
- Using open WiFi + HTTPS (SSL). This is as good as SSL is (which pretty good). There has been some talk that SSL may be compromised by the government, but I’ve not seen any definitive documented examples (but I’m going to knock off a point just in case). Rating: 9
- Using open WiFi + HTTPS (SSL) and VPN. This is about as good as it gets. Your data is double encrypted through steps A-E). Rating: 10
- Using WEP / WPA2 encrypted hotspot with HTTP. This is very similar to option 1 except you get 3 out of 4 on the first step (it looses a point for possible compromise.
Rating: 3(EDIT: I was reminded that it’s not actually fair to group WEP with WPA2 or WPA3 since WEP it seriously flawed, so I’m going to change my rating). Rating WEP: 0, Rating WPA2/3: 3
- Using WEP / WPA2 encrypted hotspot with HTTPS (SSL). Pretty darned good. Rating: 9.5
Are there any other ways the VPN could protect me?
Yes, there is (at least) one way. When you directly connect to a remote host, the host (and every hop in between) sees your public facing IP address (your Comcast / AT&T provided router address). If you use a VPN, the remote server will see a Google provided IP address. What this means is that it would be quite a bit harder for the remote server to identify who you are. Anonymity can be a good thing. 🙂
Ok, so where do I go to find a key?
There is a crowdsourced map of locations where keys have been seen. Keep in mind that locations where keys have been seen may still not show a key for you if the connectivity at the hotspot isn’t “good enough” Edit: it’s been brought to my attention that this map is no longer available. Sorry. Project Fi WiFi Spots
I don’t want Google knowing that much about me
Project Fi’s “Key” or VPN is a cool free feature that you should be happy to see.
I hope you found something in here useful.