AirTraf 802.11b Security Package
An anonymous reader writes "Being ignorant of network vulnerabilities is a happy condition for only so long. Ignorance is bliss, right up until someone with rogue access drives away with your company secrets. This article covers information about AirTraf, an open source package, which performs a number of tasks, such as determining the Service Set Identifier of the access points, and the channel it is operating under. It can tell how many wireless nodes are connected to a given access point, as well as that point's total load. AirTraf is capable, too, of polling a number of sniffers through a central polling server in order to collect the most current information. The least of your fears should be the leeching of your Internet connectivity. Industrial espionage is a growing reality that you must confront."
But like most wireless security tools, are the people with ill intent just going to turn it around and use it for their own ends?
Oh well...if the claims are correct, it will all be irrelevant when WPA releases later in the summer.
Is there any way to do triangulation if you have more than one base station? Then you could do some spatial security as well, by restricting access to particular zones (say, within your own building). I know the cell phone companies have been trying to implement E911 locating for a while ... could you do such a thing with a carefully written 802.11 driver?
Toronto-area transit rider? Rate your ride.
It's clear to me that no matter how much arm waving is done by security experts and those who stand to profit from the implementation of wireless security (cough, IBM), nothing short of tragedy can motivate American organizations to take security seriously.
Security is NOT a necessity - in fact, many of the things people are trying to "protect" these days don't need to be protected at all - security consultants just want to rake in commissions as they help their clients "secure" their data.
It's high time that these profiteers take off their Microsoft hats and start acting with the best interest of the end-user in mind.
Always treat your wireless network as a completely insecure network; the same way you treat the public Internet. This has the additional advantage that when visitors come to your company, they can use your wireless network to access their own home base. This can be amazingly useful.
Then use VPN to give your own staff access to the network, with the same security level you require for access from the public Internet.
WEP is not useful for anything than discouraging the casual bandwidth leech, if that matters to you at all.
The USSR did a ton of traditional espionage, and a million ton of industrial espionage. Their attempts at landing on the moon was done with a capsule that was a near-perfect copy of the Apollo. Their space shuttle (Buran, or whatever it was called) was an exact replica of the US shuttles. The TU-144, the Russian commercial supersonic airliner, was an exact copy of the Concorde (it was nicknamed the Concordski). Some of the cars destined to the rich russians, like the GAZ Volga, look exactly like US models, etc etc ...
This is not limited to the former USSR : all eastern block countries have done it, and China stil does heavy industrial espionage.
"A door is what a dog is perpetually on the wrong side of" - Ogden Nash
Note that WaveSEC is NOT a replacement for end-to-end security. All it does is protect you from wireless eavesdroppers. If you are using WaveSEC or end-to-end IPsec for all your network connections, you don't need WAVEsec.
-30-
In reality, you want to firewall off the AP and then use SSL to tunnel through it as you suggest. If they had built something better into the spec like IPsec (as good as SSL, but implemented deeper in the protocol stack), it would have been much better. Setting up SSL properly isn't so easy and it woould be nice to give the average WEP user something that works 'out of the box'.
See my journal, I write things there
espo
I understand where you're coming from, but EAP/TLS clients were written by people who also understand this (at least the ones I've played with). Thus, when validation of the server certificate fails, you don't get an option that says "proceed anyway". On Win XP, you get something that looks like this. No option to accept.
That's not to say that you can't turn validation off. You can, but it requires that the user go into some in-depth options on their NIC configuration. I, the evil uber-hacker, could attempt to persuade my victim to walk through these steps or, better yet, download and install a key from my evil-CA which I would then use on the evil-rogue-AP to spoof a session.
Shoot, at that point it's just as easy to persuade said user to download and install a trojan, which works equally well on both wired and wireless networks, rendering the security differences moot. And, as a bonus, the wired network doesn't even require that I construct and install an evil-spoofing-AP!
All the same, if you have a link to the demo you mentioned, please post it. I'd be interested, for sure.