WEP Broken Even Worse
collin.m writes in with news of results out of Darmstadt. Erik Tews and others there have demonstrated how to recover a 104-bit WEP key in under a minute, requiring the capture of fewer than 10% the number of packets the previous best method called for. The paper is here (PDF). Quoting: "We were able to extend Klein's attack and optimize it for usage against WEP. Using our version, it is possible to recover a 104 bit WEP key with probability 50% using just 40,000 captured packets... for 85,000 data packets [the success probability is] about 95%... 40,000 packets can be captured in less than one minute under good condition. The actual computation takes about 3 seconds and 3 MB main memory on a Pentium-M 1.7 GHz..."
Can ARC4 be used securely at all? Or are WEP's failings its own fault?
On a somewhat related note, I'm annoyed that wireless encryption was implemented in hardware. Nintendo DS's wireless is worthless to me since the encryption system can't be upgraded.
"Screw Sun, cross-platform will never work. Let's move on and steal the Java language." - Visual J++ Product Manager
Hasn't most everyone moved to WPA-PSK by now?
You know, I have one simple request. And that is to have sharks with frickin' laser beams attached to their heads!
Code up a windows binary for this exploit, and everyone will move to WPA-PSK much faster!
technical writing / development
....well, not really.
But many home users run their access point completely open and never have a problem. WEP still will make an attacker have to actually break in - negating their excuses of "well it *was* wide open , so..."
Of course, this vulenrability applies to those would wish to/need to secure their networks.
I am very small, utmostly microscopic.
Case Dismissed!
"It's the height of ridiculousness to say for those 9 lines you get hundreds of millions."
For some reason I can't get the paper to load, but anyway, does this still depend on weak initialization vectors?
- plus.php )
I know that the original attack did depend on that, and most software and basestations have since been configured to avoid those weak IVs. I know that some stuff (like Nokia's basestations) are still weak agains the original attack (at least when tested with Kismet), however, against Cisco Aironets and almost any newer hardware I haven't been able to see this weakness in action when trying out if it really works...
(Terabeam uses the term "WEPPlus" about this - see http://www.terabeam.com/solutions/whitepapers/wep
Anyway, if this is just extension of the original attack, then it still requires those weak IVs to exist.
Or is it something completely new?
Even the acronym is broken. Isn't WEP one of the contributors to the bollocksy promotion of extra bits for security instead of a better model?
This may be a dumb question, but why does TFA only refer to 40 and 104 bit WEP when the more common variants seem to be 64 and 128 bits?
G-Force music visualization
Just upgrade ALL of your wireless hardware to avoid this. Or you could simply wire up your place and have secure communications at a faster speed and lower price.
I prefer the "u" in honour as it seems to be missing these days.
I use 56-bit WEP and I've never had.... ATTN: YOU HAVE WON THE IRISH LOTTERY PLEASE respons immediately to... ...so I don't see why it is a big deal?
Some settling may occur during posting.
Cat 5 cable. It's cheaper, faster, more reliable, and more secure.
I don't respond to AC's.
WPA can also be broken, and unlike WEP, you only need to sniff one packet. Tools to crack a WPA key are freely downloadable.
I'll probably be modded down for this...
WEP insecure! Coming up at 6PM Bill Gates still really really rich.
Hardly... WEP is known to be thoroughly broken - it doesn't really matter that now it's even more broken than before - the fact remains that it's no good.
WPA has been around for something like 2½ years now, and it is a travesty if the wireless chipset you're using doesn't support it.
The simple solution is continue to use WPA, like you should have been doing for years...
Specialist Mac support for creative pros, Melbourne
And can you actually make a wireless router accept both secured and unsecured connections (or WPA and WEP connections) at the same time? So, for instance, the laptops of the house would all use WPA and the NDS would use WEP?
---GEC
I'm but the humble pupil, seeking to snatch the scratchbuilt pebble from the master's fully articulated hand
WPA-PSK is only slightly more secure than WEP. Best wifi security is to not use it.
Remember, wired is the networkng technology of the future.
Linux wireless support is OK for connecting to large corporate networks with RADIUS and 802.1x with enterprise-class WPA. I routinely do it with Ubuntu, Fedora, and Red Hat linux; it even works with Network Manager. Well, most of the time with Network Manager... Recent versions of Network Manager... And it always works with a painstakingly hand-crafted custom-compiled WPA supplicant, even on Fedora, you just have to bleed some neurons out of your ears figuring it out the first time.
But for home networks, I've only found WEP to work really well. Trying to get "personal" WPA PSK working from a linux laptop to a commercial broadband router like a linksys or FIOS box is brutally painful, even with decades of experience, and if you have Network Manager flailing around hijacking your wifi hardware every few minutes it's even worse. If you wanted a rock-solid, high-bandwidth wireless connection with enough encryption to convince casual wardrivers to use the neighbor's connection instead of yours, you just ran WEP-128 on your dd-wrt box, and happily connected up with Network Manager or iwconfig... but if the next version of the stumbler's going to crack your WEP nearly instantaneously the weak deterrent effect of WEP just went out the window!
There's someone working on a firmware patch (or some such), but it looks dubious to me and also requires a specific flashcart: http://geekboy.ca/wifi/?cat=2/ Also it's probably possible for DSLinux (http://www.dslinux.org/) to support WPA and wpa_supplicant has been ported but it requires some more work on the driver before it'll function properly. Trouble is none of the current dev's are really au fait with WPA, so any help is gratefully accepted.
If you have no choice but to use WEP, then you should strongly consider using a VPN between clients and the connected network!
In a corporate environment where it's hard to control who knows the passwords, do NOT bridge the wireless network to your secure cabled network but put it on a DMZ and allow limited services out to the internet, and even fewer into the corporate wired lan.
My understanding is that it should be easy enough to implement WPA on older (.11a/b) hardware, but companies much rather sell end user new hardware (.11g etc.) than spending development time to upgrade old hardware (that does not generate additional revenue.) This is evident in that Apple's old AirPort (.11b) does support WPA but other venders' (that would include YOU, Linksys) old .11a/b products do not.
ELOI, ELOI, LAMA SABACHTHANI!?
This isn't really news. It's pretty smart that they have managed to crack WEP with so few IVs (it usually takes about 200,000 for 64bit and just under a million for 128bit) but in reality this doesn't change (or expose) WEPs inherent vuneribilities at all, for example I am currently doing my dissertation on wireless security and in tests WEP64 on average can be cracked in about 3 minutes and WEP128 in about 10 minutes so getting this down to a minute doesn't really change the fact that a hacker could capture enough packets simply by hanging around and drinking a coffee using the "old" tools.
An interesting sidenote is that the amount of time a hacker needs to be near a target WLAN for WPA-PSK is measured in seconds making it much more insecure if it has a weak passphrase than WEP is even now with crack times under a minute.
Please if you want a secure home wireless network choose WPA-PSK and make the passphrase as long and as abstract as possible, nothing else is safe -and if you have the cash... buy a radius server
Since this is Slashdot, I request a community service: Come up with a script/whatever where this is simple.
Can anyone confirm any of this? I find it interesting that while the paper was published today, it was received on April 1st.
See: http://eprint.iacr.org/2007/120
If the cards don't do WPA, then cheat. Most wireless-capable routers that don't support WPA -do- support IPSec, as do most laptops and other portable devices. Sure, you're not doing hardware encryption then, but the speed of most modern processors vastly outpaces most wireless connections - you can afford the cycles on an IPSec tunnel to the router. In theory, this is better than WPA, as IPSec is a more mature standard with a lot more people looking at the design.
It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
The built-in wireless card in my laptop is the only thing keeping me tied to WEP (my Palm uses BT so that's not an issue there). It's one of those weird combo mini-PCI cards that also drives the dial-up modem (HP zt1100 series laptop). If I could find a combo card that supported wireless G and WPA I'd upgrade in a heartbeat. I've searched the net for one, but it seems like mini-PCI cards are in this amorphous, murky world where it's impossible to locate manufacturers and specs.
That is indeed what I do as soon as I run into anything "esoteric" (that is, anything that a mac or windows PC can handle effortlessly but which chokes my linux machines HARD).
I just drop to a command line, superuser myself (sudo is too much typing, so I re-enable su on my unbuntu boxen and macs, it's pretty easy), kill network manager, iwlist to get the network, cut and paste the fiddly bits into an iwconfig line, swear repeatedly because each wireless driver has idiosyncrasies that need pampering (try using a hex key that looks like an alpha key - BEADFEEDBEADFEEDFEEDBEADBF for example - some drivers will let you use a special 0x prefix, others just don't seem to be able to cope), use bash command line editing to fix as appropriate to the particular hardware I'm using, then bring up a DHCP client (of course, I have to figure out which client this distribution uses since they have totally different command line syntax) to get the interface useable, and then go back into X where I can use a browser.
Sure, it's simple. My dad, an octogenarian rocket scientist (retired), can do it in less than a week if he also has a windows PC handy so that he can look up things in Google! I can do it myself in mere minutes! And using su for this instead of sudo has the side effect of not leaving WPA keys in the history of an unprivileged account, incidentally.
But you know, it's really annoying to watch the people around me just click and go with their Windows and Mac laptops. I guess nobody should use a linux computer wirelessly unless they not only have leet skillz, but also lots of time to spend typing things and memorizing connectivity tricks? Why are we bothering with GUIs, then? Linux wireless works perfectly in some subset of configurations (that happily includes most corporate and Starbucks-type rigs) but, in my personal experience, does not come close to mac or windows wireless.
Ever try to connect to an Intel Pro-Wireless 802.11a AP with linux on a Dell laptop? Turn off Network Manager and prepare to spend some time dicking around. In windows, it's a couple of clicks and type the key... done.
The only real conduit one needs in a house are a crawlspace and an attic.
> That is indeed what I do as soon as I run into anything "esoteric" (that is, anything > that a mac or windows PC can handle effortlessly but which chokes my linux machines > HARD). Effortlessly? Like I said the only cases for me are when DHCP is off, which I don't see often - and how effortless can your "octogenarian rocket scientist" dad configure Windows or Mac for static IP with custom Gateway, custom DNS-Server? Yeah, that's what I thought. But I do get your point. Of course those cases should be solvable in the GUI as well, and from what I hear that's where things are going (yes, yes, linux is lagging behind in this regard). But my comment was in response to claims that "it doesn't work at all" and "network-manager keeps preventing me from doing this and that". I never claimed this was newbie-proof solution. Or that it shouldn't be improved upon. > Linux wireless works perfectly in some subset of configurations (that happily > includes most corporate and Starbucks-type rigs) but, in my personal experience, does > not come close to mac or windows wireless. Ack. (Though, I admit I did enjoy reading your over the top comment. ;))
Slashdot editors suck at grammar. Obviously, the words they were looking for was supposed to be more brokener.
Either one on it's own can be secure. It's the combination of ARC4 and WEP that makes this bad.
No sig today...
For the most part who cares? So somone piggybacks on you.. Is that really such a big deal?
Either you are at home and are sharing some internet with a neighbor by accdient, or you are a company that has everything else locked down enough it doesn't matter anyway.
if you have to be *really* secure you dont use wireless in the first place.
---- Booth was a patriot ----
If I'm running on an unencrypted wireless network, but the little lock-symbol appears on my browser, then even if someone is listening in, they can't recover any passwords/cc-numbers I enter into web-sites, correct?
Why does the existance of an encrypted disk allow the Judge/Jury to presume that you are guilty? I think that an encrypted disk tells them nothing. Assuming one: that you are using something decent like CFS or TrueCrypt and two: that you're smart enough to use it for all of your illicit material you've completely denied the prosecutor any evidence that you committed a crime.
I'm collecting 7 beacons per second, it's aprox. 3 valid IVs each 10 seconds.
:P
I need many days and months to collect 800,000 IVs!!! It's bad milk!!!
I want to speedup it, i want inject 50,000 packets/s to receive 50,000 beacons/s
but the device can't inject packets. I hate to obtain 7 beacons/s.
Why? Why? Why of this awful cracking?
Many sites are WPA2 and no WEP. I'm hating it a lot.
My ultimate action is to go to my car with my laptop and drive randomly for hijacking.
I'm sure that there are many WEP ESSIDs. I'm a suicide hijacker.
No, you're doing it all wrong, this is a glider:
oxo
oox
xxx
I'm not sure what yours was.
Ewige Blumenkraft.
correct.
but also look at URL to see that it is https and not http
if it says http (Bank of America for example) then it is not secure despite what bank of america claims on its lie filled site.
only trust https
Enough already, just use mac filtering and only let in what is needed.
Success is not the result of spontaneous combustion, you must set yourself on fire.
Actually you can still do a man in the middle attack but i think it's pretty obvious, ie a popup warns you that the cert is from an untrusted party or something.
This is a joke. I am joking. Joke joke joke.
You cant break WEP in Russia, in Russia WEP breaks YOU
Make SELinux enforcing again!
This will help, sure, and be quite a detriment (since hackers will then need to figure out one more detail before being able to own your wireless network); but the fact remains that thanks to things like macchanger and other utilities, a MAC address can be very easily spoofed.
Plus, once an attacker has enough packets, he or she can divulge the necessary MAC address from those packet headers, so it's not really as great an aide as many claim...
Is dead.
With our current MO towards encryption, there is always a way to break it- it's just a matter of computing power, and that's a metric that's ever-increasing. It's no longer sufficent to think a method is strong simply because of the amount of power it takes to break it- because that power will be available to the public next week.
We need to rethink encryption as a whole, or rethink what information we transmit electronically.
As others have mentioned, the Nintendo DS only supports WEP, and that is a serious problem. Mostly, it's serious because most consumer wireless access points will only support a single type of encryption at a time.
I have two physical WAPs, one just for DS, and one for everything else. It's a problem. Nintedo needs to take some flack before they are going to realize that they screwed up.
There probably isn't anything that can be done to fix their product.
Encryption is only one of the keys to home wifi security.
Encryption can be cracked but if the leecher does not get a signal, (s)he can not get any packets to decrypt:
Limit the power of the signal so it does not go far beyond the walls of your home.
P.S. Mod this AC insightful
you are actually right, there are 35.27 oz in a kilo.
but where i come from it's as if there were 36.
why?
because 9 ounces is a 'nine bar', and a 9 bar is quarter of a kilo.
it's the point at which you start to get 'wholesale' prices (for weed) and also the changeover from imperial to metric.
the discrepancy may be partly explained by the fact that an ounce of weed is usually exactly 28 grams.
all this in the uk, where our measurements are fucked up anyway, half the country use imperial and the other half metric (for non-drugs related measurements).
my password really is 'stinkypants'
Most people who actually bother to secure their wireless use WEP as a very basic precaution. They aren't really concerned that someone is going to spend time trying to break into their system, they're just discouraging casual visitors. If someone really really wants to break into my extremely boring home network, I'm sure they could, but they're more likely to use the two unsecured networks I can detect from my living room. Frankly, its just not worth the effort for me to go to extremes to protect my network when the likelihood of a real attack is so small.
Life needs more saving throws.
Any Linux live CD distribution wich uses this new method released ?
Seriously, Dad uses an old iMac to keep his books, a windoze XP box the IRS provides him with gratis (he volunteers at the senior center to help old folks who can't figure out their taxes) and the Ubuntu box I built for him to get his email. He has no problems operating any of these systems despite his age and physical infirmities; he's a pretty smart guy.
I've seen him use his windows laptop to connect to an encrypted wireless network. He's had no training with RF since he was a radio repairman in the Korean War, doesn't know 802.11 from a V8, but he just waltzed right in there, nobody had to do anything but tell him the key. I eventually gave up trying to connect to the same network with one of my linux laptops after a half hour and rebooted into windows... and I got right in too! Since I am much more familiar with linux than I am with windows, this was frustrating and annoying.
Anyway, I'm glad you enjoyed the rant.
Do you use a packaged distribution, or do you custom-compile your drivers and/or kernel?
Do you have any problems with OpenSuSE stepping on your drivers during routine updates, or does everything survive OK? Are you using 802.1x by any chance?
I haven't used SuSE for several years. Maybe I should revisit! I've been pretty dissatisfied with Fedora, so I'm running Ubuntu a lot these days.