Ok, so I’ve been going through a few airports lately. I noticed something strange at the ones at which you’re usually required to shell out some cash to use teh intarweb (arrangements with Boingo or T-Mobile or whoever). I use a Mac-- when I detect wireless networks, the whatever-pay-service and whatever-airline’s closed ‘admiral’s club members’ networks show up as one would expect. However, in addition, a couple of computer-to-computer networks always show up as available, and one of them invariably shows up as “Free Public Wi-Fi.” What is this about? Is it a lure by someone to hook up people with unsecured machines to riffle through for hoots? Or is it some altruistic techie who shares an external network with random strangers and I simply don’t know how this works? What’s the deal here?
I vaguely remember reading something about this a while back. Google found this :-
If that guy is right, it’s a quirk of the way Windows XP remembers wireless connections, and entirely harmless.
Cache, Johnny, and Vincent Liu. Hacking Exposed Wireless: Wireless Security Secrets & Solutions. New York: McGraw-Hill, 2007.
Well, what do you think about it now?
William B-- that’s exactly it, I bet. I’m not going to shell out credit card info for airport wi-fi anyway (so hooray PDX and Denver with their sane free wi-fi) and my computer’s pretty secure, but this looked much too odd. Interesting.
I strongly recommend looking into the risks surrounding public hotspots.
The book I referenced above covers the subject fairly well; next time you are in a book store, take a gander at the chapter I referenced.
The author not only discusses several schemes for setting up bogus hotspots that are man-in-the-middle attacks, but he shows several step-by-step examples, with screenshots, of how to use commonly available network tools to hack other clients sharing the same hotspot you are on, among other things.
In one example, he ran some diagnostics that pointed out one XP machine attached to the free access point that was missing a critical security patch. He then typed in a simple command that automatically hacked the machine and presented him with a remote command prompt on that XP machine. He then added an admin local user and enabled remote desktop on the victim machine.
The fact that the tool simply told him “machine at 1.2.3.4 is missing patch X” and allowed him to deploy any of dozens of payloads via many dozens of available exploits is unpleasant. Pretty much script kiddie material, no uber-blackhat needed.