Linked by Igor Ljubuncic on Mon 2nd Apr 2012 15:41 UTC
Permalink for comment 512757
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
More News »
Sponsored Links



Member since:
2006-05-12
Do you actually look at the certs given to your HTTPS connections? In a "hostile" environment trusting HTTPS to be secure isn't much better and often gives a false sense of security. It's pretty trivial to just proxy any HTTPS traffic for a user and unless you actually look at the cert you'll never know. I will admit that if your data stream between you and siteA is legit that people in between can't sniff it, but if you're starting out in a hostile area it can't be trusted.
The only way to be secure in a hostile environment is a key based structure (SSH, VPN, etc..) where you already know the key on the other end. ie: you SSH to your home box and get a prompt for a new key, that you know you've been to before, one would be a fool to continue.
A bootable CD distro and a USB key with your various keys (SSH, VPN, etc...) pre-setup is a good way to go.
I'm not saying this isn't a pain in the ass, but unfortunately real security normally is these days.