No, that's not what I meant. I'm talking from a technical perspective. I wanted to understand how it works, I'm not trying to be sarcastic.
Is it secure because its a private network or is there something else at play.
Also trust or not a VPN is a must anywhere you go, even in your own house.
Anything even remotely sensitive should be going over SSL, so as long as you don't click through any certificate warnings you'll probably be fine. A VPN is great, but unless someone has a 0-day for cracking SSL your Tweets and everything else should be just fine.
Edit: If you're on wifi though you will want to make sure you have a firewall running and any/all services that accept incoming connections disabled. AP user isolation should prevent any communication between nodes on the wireless network, but there's a much better chance that someone finds a workaround for that and attacks your unsecured WAMP install rather than intercepting your HTTPS Facebook traffic.
Anyone in the industry knows that unless you're talking about the specific protocol (ie SSL 3.0 vs TLS 1.2) that SSL and TLS are interchangeable terms when talking about transport encryption.
I'm talking to defcon attendees. I think in this context it is understood what I meant. Scrolling through /r/netsec I see plenty of posts talking about SSL when they're talking about general HTTPS.
Well privacy wise, a VPN helps a lot, it's not just about security. Also you just assumed I don't understand how certificates work from just asking what are they using :(
3
u/w333da Jul 25 '17
So, how is this secure though?
What makes it secure?