Public network security?

DellAxim

Gawd
Joined
Feb 14, 2003
Messages
999
Let's say I'm connected to a public wireless network at a hotel or something. Is it possible for the owner of that network to track things like what web pages you've been too, files you've downloaded, or even passwords? :confused:
 
And if you are overseas or at hotel owned by an overseas corp, then it is actually quite likely.. The new face of corporate espionage.. You don't need a mole anymore..
They prolly don't care about the porn or the e-mail to the family though..
I would never use a hotel's network for sensitive: data transfers, emails, or to log on to a remote server at work or home.. I would not trust even encrypted packets, personally, on someone else's network....
 
If you're at a hotel, just VPN back to your home/business/whatever. As long as you've got a personal firewall, and you're using IPSec-IKE, using 3DES or AES as your encryption protocol, have split-tunneling turned off, and are using a good authentication mechanism with IKE, you should be fine.

If it were that easy to crack, Fortune 500 companies and government agencies wouldn't be allowing employees to use it.
 
If it were that easy to crack, Fortune 500 companies and government agencies wouldn't be allowing employees to use it.
I generally agree with the assessment that it's strong, but this last statement is silly. I have a firewall/vpn endpoint out there running DES. Not 3DES, just DES. Why? Because at the time, we couldn't afford 3DES, and the model with just DES was on the list of approved firewalls/vpn clients.

Government agencies have a hard enough time finding their ass with both hands, and are hardly worthy of holding up as an example.
 
an IPSec VPN should be sufficient in keeping the data safe. I wouldn't trust the hotels network though, and the hotel isn't the only ones you need to worry about, plenty of the guests will see your traffic too.
 
I generally agree with the assessment that it's strong, but this last statement is silly. I have a firewall/vpn endpoint out there running DES. Not 3DES, just DES. Why? Because at the time, we couldn't afford 3DES, and the model with just DES was on the list of approved firewalls/vpn clients.

If you're still using DES, that is silly.

Government agencies have a hard enough time finding their ass with both hands, and are hardly worthy of holding up as an example.

Some of them are perfectly worthy of holding up as an example, and have their act together quite well.
 
Let's say I'm connected to a public wireless network at a hotel or something. Is it possible for the owner of that network to track things like what web pages you've been too, files you've downloaded, or even passwords? :confused:

Yes, for unencrypted pages. As I understand it, though, SSL sites would still be safe; they're designed with man-in-the-middle attacks in mind.

A cool link about what you can do with your access point: Upside-Down-Ternet
 
If you're still using DES, that is silly.
No arguments. In fact, it's a point I raise at least once a week. However, given how thing work in my city, it's still there and not going anywhere any time soon.
Some of them are perfectly worthy of holding up as an example, and have their act together quite well.
Some are, sure. Most are run by politicians. Worse, politicians with a loose grasp of reality and no concept of technology. It's magic to them.

As I said, I agree with the rest of your post, just not about using large corporations and governments as some sort of yard stick.
 
As I said, I agree with the rest of your post, just not about using large corporations and governments as some sort of yard stick.

I think I see your point of view, and if I'm interpreting it correctly then I agree with it. My point of view is more from a risk-acceptance point of view. Very large companies and government agencies would not be using IPSec-based remote access if it were not very secure. They have a TON of sensitive data to protect. I think your point of view is from a "do they implement it properly" perspective (correct me if I'm wrong) - but setting that debate aside for a second and focusing on the technology itself when it is implemented properly, it is very secure.

The initial point I was trying to get across is that GORANKAR was making it sound like (at least to me) that there is no secure way of transmitting sensitive data across an insecure medium. That is really not the case. If you have IPSec-IKE setup correctly (including the back-end stuff after you get past the tunnel), just about the only people who are going to be able to get your data are those with the ability to crack the encryption method. If you're using 3DES or AES and someone is capturing your traffic who can crack that in a reasonable amount of time, including all the re-keying during their capture, then you're pretty much screwed no matter where you go on the planet, and you should probably just kiss the Internet goodbye forever. Of course, someone can always compromise the host, but that is not directly related to the security of IPSec-IKE. That is an end-point security problem, which is a whole other discussion......................
 
Back
Top