Am I okay without a VPN on public networks if I use HTTPS?
I keep hearing on VPN ads that you have to use a VPN to not have your login information stolen. So far I have been using Cloudflare WARP to be safe enough. However, if I am using an HTTPS website, do I really need a VPN or WARP? Will an attacker on the same network as me be able to access passwords transmitted over HTTPS?
Yes you're good. The ads are basically lying, or at least vastly overblowing the importance of VPN. It's nice to have in some situations, but no, hackers won't immediately pwn you as soon as you connect to a McDonald's wifi.
It was just a few years ago, before everything on the Internet was HTTPS, that using a public Wi-Fi was pretty dangerous, in terms of exposing your login credentials and traffic.
Even today, it's possible that some random sites might be HTTP only, but it's unlikely.
But even then, anyone on the same network can still see what sites you are going to, just not what's being said.
This is not completely true. Try to look at email from shops (for campaigns etc.), and you will see tons of click-tracking links that go through HTTP. Any of that gets hijacked, and you have an avenue to be phished. DNS integrity is key, and a VPN being a layer 3 control (i.e., at the network level, not the application level) helps preventing some of these attack vectors.
In this particular instance they are talking about hosting a Virtual Private Network (VPN) at home, not connecting to a commercial VPN service. And this is definitely the best way to do this. HTTPS isn't authentication, unless OP uses client certificates, meaning anyone can reach the hosted service and try to exploit it.
It's not particularly easy to find a trustworthy VPN, but it's not particularly hard to find one you'd trust more than whatever random public wi-fi you've found while on the road. Your stock reminder that we can never trust anyone is not really useful here.
Using a good VPN is one way to sanitize the whole network environment when you have no reason to trust even the router you're connecting to, avoiding quite a few risks besides that of someone passively analyzing your traffic.
You communicate via snail mail with someone. Both ends know the address of each other. So does the postal service delivering your mail. Everyone opening your letter can read (and with some work even manipulate) the content. That's HTTP.
Now you do the same, but write in code. Now the addresses are still known to every involved party but the content is secured from being read and thus from being manipulated, too. That's HTTPS.
And now you pay someone to pick up your mail, send it from their own address and also get the answers there that are then delivered back to you. The content is exactly as secure as before. But now you also hide your address from the postal service (that information has the guy you pay extra now though...) and from the one you are communicating with. That's a VPN.
So using a VPN doesn't actually make your communication more secure. It just hides who you are communicating with from your ISP (or the public network you are using). Question here is: do you have reasons to not trust someone with that information and do you trust a VPN provider more for some reason? And it hides your address from the guy you are communicating with (that's the actual benefit of a VPN for some, as this can circumvent network blocks or geo-blocking).
Long story short: Do you want to hide who you are communicating with from the network you are using to access the internet? Then get a VPN. The actual data you send (and receive) is sufficiently secured by HTTPS already.
But encrypting already encrypted HTTPS data is largely irrelevant (for that simplified analogy) unless you don't trust the encryption in the first place. So the relevant part is hiding the HTTPS headers (your addresses from above) from your the network providing your connection (and the receiving end) by encrypting them.
Unless of course you want to point out that a VPN also encrypts HTTP... which most people have probably not used for years, in fact depending on browser HTTP will get refused by default nowadays.
why would you leave out the role encryption plays in the VPN tunnels? And that VPN providers are independently audited and subsequently rated for their data log retention rates?
Then you should probably point out to OP which VPNs are independently audited and not keeping data or not operating in any country requiring access by law enforcement. As everything else would totally defeat your "but government actors"-argument from above.
Depends on the context. If you are at home on a wired / non public connection....HTTPS by itself is probably good enough for protecting your password / credentials from your general "web goblin" type of hacker.
However, if your device is compromised with malware (keylogger or whatever) then neither HTTPS nor a VPN can protect you.
HTTPS uses a special key sharing algorithm to safely encrypt your data so that it's relatively secure to transmit across the internet. Even if a man-in-the-middle intercepts it, they can't decrypt the data.
A VPN is an extra layer of security that hides your session from your internet service provider, or your boss, or random people on the WiFi at your local coffee place, that sort of thing. Using VPN is a good idea, but it's not a magic solution, and it's not always necessary. The VPN helps hide things like the websites you are visiting, your IP address, stuff like that. It also encrypts your traffic in a "tunnel" which is nice, but HTTPs packets are already encrypted. So HTTPS over a VPN is doubly encrypted.
Security-wise, you do no harm using both. However, using a VPN can be a little bit slower and some services (like the Google platform and major video content streamers) really don't like it when you use a VPN. You can sometimes get around this by purchasing a dedicated IP address from your VPN service provider, but that usually costs extra (on top of whatever you may be paying for the VPN service itself).
And...a dedicated IP may or may not fool those picky content streamers. They have gotten pretty aggressive about blocking VPNs because they know people use them to get around regional content lockouts and restrictions.
The best way to think about a VPN is a different ISP, when you activate a VPN your traffic goes through an encrypted tunnel through your primary ISP to the VPN, then the traffic is decrypted and dumped onto the internet. If you trust your VPN more than your ISP (either because they are more trustworthy or because they don't know who you are) then it is a win. If you trust your ISP less than your VPN it is a loss.
One important thing to highlight is like public WiFi that can allow people nearby to try and sniff your traffic. A VPN can be quite effective here even if you trust the ISP "behind" the WiFi.
Replying to myself to add: if you use a VPN to hide your surfing habits from your boss, the security team can tell you are using a VPN. They may or may not care, it largely depends on where you work and if you're using your device or a company device and the "corporate culture" of the place you work. Just have a cover story / explanation ready to go if you roll the dice on this one. If you work for a large corporate bank or something like that, I wouldn't even try it.
a vpn can totally MiM if they force you to use their cert.
upstream server ssl <-> vpn client ssl <-> vpn MiM <-> vpn server ssl <-> you
Even with no MiM, VPN is going to know where you are going and how long you are there, and any unencrypted comms (UDP / torrent, funky http URL) are just … there.
I would assume consumer “privacy” VPN traffic is easily monitored by state agencies since there are fixed points of entry & egress?
Any corporate VPN worth its salt is totally MiM all traffic; usually spells it out in the sales brochure.
VPN is mainly good for bypassing region blocks (like Netflix) or as a tunnel through company firewalls. All other advertised use cases are either overstated or outright false.
You might not know if an app on your computer uses encryption when it communicates. And you dont know if a ssl cert has been exposed but not revoked yet. So no, you cant trust https alone.
And I've seen just how easy it is to setup a fake wifi and have peoples phones be autoconnected to it because the victims have an old public network in the "remembered networks" list. On a dev conference.
So i use either use vpn or a private mobile network. Well, honestly I actually don't. I suck at practicing what I preach. Convenience versus risk.
There's a possibility, but not a big one that any given WiFi has an decrypting proxy in place. Your device should be giving a big warning flag if a certificate was found issued by an untrusted cerificate authority. It's possible if someone like Google or a government body ran the portal that they could issue 'trusted' certificates for sites on the fly through such a proxy and grab whatever they want while it's decrypted mid stream.
The whole premise of HTTPS as security is based on the notion that the CAs at the end of the chain are trustworthy and wouldn't do something like that, but it is possible.
Depends on your risk tolerance. I'd say if you have a good firewall and your whole system (not just the web browser) is set up to use DNS over TLS, you'll probably be fine.
Personally I would use my own cellular Wi-Fi hotspot over a third party VPN. A VPN … unless you are running your own … is just a giant honeypot for snagging everything you do.
The only way you know it’s not happening is you don’t.
An in country cellular service at least can be assumed not to sell your data to a cyber crime group.
You can ARP spoof a network and also serve spoofed certs resulting in the ability to resolve them. But I can see, if your not an expert, it's hard to see the difference between reality and Navy CIS
This is pretty misleading due to its brevity, an attacker on the same network can determine what website you're going to but not the content being exchanged. A VPN moves the threat of having your browsing destination determined to the VPN provider from the local network.
That said, modern WiFi encryption does prevent other devices on the network from eavesdropping, so the attacker would have to employ a more involved attack (e.g. ARP spoofing) in order to even see the destinations.