Beware these VPNs
-
@Larry said in Beware these VPNs:
@George-K said in Beware these VPNs:
@jon-nyc said in Beware these VPNs:
I’d pay to watch the World Cup, but nobody will let me, so I do this.
that really good German pr0n?
"Ooh ya, pull that plow, baby! Pull it! Pull it!"
You forgot the umlauts, heathen.
-
Ax, do you trust the WiFi in, say, Hiltons? From what I can tell they have a contract with att to provide it everywhere.
Or Starbucks?
I regularly trust these and others but I don’t go to my bank or vanguard or whatever. I would only do that over the cell network
-
Yeah, but typically I’m reading online news or twitter or posting here. I’ve thought about the WiFi issue before and then fugired, do I really care who sees this?
-
How I see various public or semi-public Wi-Fi hotspots in North America:
-
Marriott, Hilton - won't login to financial accounts or do any software update over their Wi-Fi, but otherwise OK with using them for most things. Stayed in enough of them to be able to tell whether a particular property's Wi-Fi/Internet access system has been brought up to the usual Marriott or Hilton standard. Every once in a while I got into a property newly acquired by the chain and the Wi-Fi doesn't look or feel right (e.g., the way the network is named, the way the login process is handled), then I just treat it like I treat Wi-Fi provided by "other hotels".
-
Transportation hubs (airports, train stations, etc.) - the challenge is, when you see a Wi-Fi network name like "ATL Free Wi-Fi", how do you know that it's really operated by the "ATL" airport? If there are obvious, publicly posted signage or public announcements that collaborate that "ATL Free Wi-Fi" is indeed sanctioned by the airport, then I treat it like I treat the Marriott or Hilton Wi-Fi. Otherwise I avoid them.
-
Regulated utilities (Comcast's XfinityWiFi, the cable consortium's CableWiFi, AT&T Wi-Fi, T-Mobile Wi-Fi, etc.) - If I can access them using the HotSpot 2.0 standard, then I treat them like I treat the Marriott or Hilton Wi-Fi. Otherwise I avoid them (because I cannot verify whether a network that's named "AT&T Wi-Fi" is indeed operated by AT&T).
-
Other hotels, restaurants - won't login to any site that requires that I login, won't do any software update over them, but I otherwise don't mind using them, especially with sites that are accessed using HTTPS/TLS. This, too, is predicated on me being able to verify that the Wi-Fi network is sanctioned by the proprietor (e.g., there are posted signage or the front desk tells me that "XYZ Wi-Fi" is indeed an amenity provided by "XYZ hotel" or "XYZ restaurant"). If I cannot verify that, then I avoid the using the network.
-
-
I think some of you guys are a little hysterical.
I'm happy to use any WiFi, regardless of how "trustworthy" it looks or how encrypted it is. I also don't hesitate to do financial stuff etc. via it.
"Security by obscurity" doesn't work. Encrypting things twice or thrice doesn't increase safety. Taking a wired connection over wireless doesn't increase safety. You choose one good tool that you can trust, then you can forget about all the other mediocre tools.
For internet communication, that tool is certificates and strong encryption, as in HTTPS and SSL/TLS. There are no realistic scenarios how even a malicious attacker who completely controls the WiFi can bypass those security mechanisms.
-
@Axtremus said in Beware these VPNs:
When you are not at home (where you operate the Wi-Fi network) and not at work (where your employer operates the Wi-Fi network), just use your mobile phone's cellular data to get onto the Internet, tether your laptop through your mobile phone if you need to get online with your laptop.
And how would that improve security? It isn't very hard to fake an access point for cellular data ("IMSI catcher").
-
Overall, I would say that if you make sure to get a few things right:
- configure your email to use strong encryption and certificates and disable potentially dangerous attachments
- use a modern browser and an operating system with the latest security updates
- pay attention to the usage of HTTPS, the validity of certificates, and warnings about security issues from your browser
- make sure that any other non-browser-based communication that is security-relevant uses strong encryption and certificates
- don't install stuff from random internet locations.
then this will contribute 1000x more to the safety of your internet usage than using VPNs, avoiding public WiFis, etc. For instance, if you use a VPN, then the part of the connection from the VPN provider to the host you are communicating with is still unprotected. If you use a wired connection instead of wireless, this only changes the place where an attacker needs to attack but it doesn't make it inherently more difficult.
Choose the one right tool for the job instead of the combination of multiple mediocre tools.
-
Cellular data — once you get to 3G or 4G LTE, mutual authentication kicks in and your phone verifies the cellular service. The cost and sophistication to spoof a cellular service that can fool the mutual authentication mechanism are high enough to discourage most hackers. No “mutual authentication” with 2G or older cellular standards, but you’ll notice the dismal speed when your phone’s connection is somehow downgraded to 2G.
Avoiding untrusted networks — once your machine is attached to a network, it’s not all about you making sure you use only TLS to connect to other sites/servers, but also about exposing your machine to attacks by others from that network. This is where keeping up with OS security updates helps. iPads and iPhones do better than most Android phones in this regard because Apple is pretty good with making sure that new iOS upgrades are compatible with most iPhones and iPads out there. But Google cannot do the same because even after Google releases a new version of Android, it’s still up to the OEMs (Samsung, Motorola, HTC, etc.) to pick up that new version of Android and customize it for their phones and then make those customized versions available to the end users. Even today I still see name brand Android phones that are “stuck” with older Android OS that is one or two major releases behind the latest.
-
Ax, the way I understand it is that first of all there are all kinds of loopholes due to required interoperability with 2G network, and secondly, you could still do a "man-in-the-middle" attack and just use the authentication replies from the base station. You can easily find "a DIY IMSI catcher for $300" tutorials on the internet.
Or, for that matter, you could just listen passively to the cellular traffic. Yes, it's encrypted, but so is https.