Hi,
A wireless key can be cracked within 1-4 hours, I have written a tutorial on it step by step including all the software and drivers needed!
It is on www.hackersinside.com

Thanks and Happy Cracking!
-HI

1-4 hours? I did one in about 5 minutes yesterday.

Jeez, I see why he said 1-4 hours. The howto is for fucking Windows. You'd have to be gathering in passive mode the whole time, without any injection attacks.

1-4 hours? I did one in about 5 minutes yesterday.

Jeez, I see why he said 1-4 hours. The howto is for fucking Windows. You'd have to be gathering in passive mode the whole time, without any injection attacks.

This.

Honestly, you must have some crappy software running, or a terrible connection... No, even with a terrible connection, friggen BackTrack, or any Linux-based tool for that matter, can do it in way less that an hour.

This.

Honestly, you must have some crappy software running, or a terrible connection... No, even with a terrible connection, friggen BackTrack, or any Linux-based tool for that matter, can do it in way less that an hour.

Are there wep cracking tools for Linux? All the ones I know of are for GNU/Linux... ;)

Are there wep cracking tools for Linux? All the ones I know of are for GNU/Linux... ;)

http://i70.photobucket.com/albums/i91/O__RLY/akjladncdkk7jjnvi0.jpg

LOL @ site spamming

http://i70.photobucket.com/albums/i91/O__RLY/akjladncdkk7jjnvi0.jpg

LOL @ site spamming

I think that picture is a good example. I'm cool, laid back, hip, etc. The people who say "Linux" are just old farts who parrot whatever they see on CNN.

Wanna be cool? Say GNU/Linux. It's hip. It's trendy. It's shiny.

Wanna be cool? Say GNU/Linux. It's hip. It's trendy. It's shiny.

Is that thing back? I remember a ton of people doing that a year or two ago, constantly correcting me when I said Linux, and then it kind of dropped off... Oh boy.

I don't know what the big deal is really... seriously, most people know what you're talking about when you just say Linux. You don't have to say GNU/Linux all the time.

I admit, sometimes I get pretty annoyed about technicalities like that, but come on, you come off like a prick when you say "it's not Linux - it's GNU/Linux! Use the correct terminology!"

just sayin...:rolleyes:

I don't know what the big deal is really... seriously, most people know what you're talking about when you just say Linux. You don't have to say GNU/Linux all the time.

I admit, sometimes I get pretty annoyed about technicalities like that, but come on, you come off like a prick when you say "it's not Linux - it's GNU/Linux! Use the correct terminology!"

just sayin...:rolleyes:

Well, there are a lot of really good other reasons for why you should say GNU/Linux instead of Linux. They're all good, but it's also just the right thing to say, so I open with that.

This isn't the thread for it though. So speaking of WEP-cracking, does anyone else have an annoying habit of leaving kismet open when they're trying to run airodump, and it lets you do it, but you realize you're capturing like 10 IV/s because kismet is still goddamn channel-hopping? Pisses the shit out of me.

So speaking of WEP-cracking, does anyone else have an annoying habit of leaving kismet open when they're trying to run airodump, and it lets you do it, but you realize you're capturing like 10 IV/s because kismet is still goddamn channel-hopping? Pisses the shit out of me.

God dude, I know exactly what you mean! When I first started cracking WEP, I did this and it drove me insane because I couldn't figure out why! I was looking up all kinds of specs and drivers on my wireless card, double-checking every inconceivable detail, and then after nearly a week, I realized that is was thanks to kismet... God, what a horrible week that was.

Yeah...if you're within a reasonable range, and using GNU/Linux, WEP can be taken care of in 10 minutes or less.

Only problem I had with this was my laptop kept jamming up. Full system freeze. Been a while since I did this, but if I remember correctly, it was when I ran airodump -ng to bump up the IVS.

Pain in the arse, never did get it working properly on my laptop. And there were issues with Kismet in the BackTrack 3 release I had. By issues I mean it wouldn't open...

Eventually I used another laptop, and everything worked fine. Anyone encountered anything similar? If I can get this to work correctly, then I'll be setting up a dual boot.

Pain in the arse, never did get it working properly on my laptop. And there were issues with Kismet in the BackTrack 3 release I had. By issues I mean it wouldn't open...

Eventually I used another laptop, and everything worked fine. Anyone encountered anything similar? If I can get this to work correctly, then I'll be setting up a dual boot.

Yeah dude, I was running it from the live disk for a while with the same problem. I burned another copy at a slower speed, and it resolved that issue as well as a resolution problem I was having.

I have yet to get around to getting BackTrack to dual-boot, bu I'd like to at some point.

Yeah dude, I was running it from the live disk for a while with the same problem. I burned another copy at a slower speed, and it resolved that issue as well as a resolution problem I was having.

I have yet to get around to getting BackTrack to dual-boot, bu I'd like to at some point.

Ah, fucking fantastic :D So all you did was burn at a slower speed and airodump-ng stopped locking up the machine? Strange. What speed did you burn at by the way?

Has anyone tried using two interfaces? I went from getting 30 ivs/sec to like 250 ivs/sec. My neighbor had a ten byte encryption key that only needed 20,000 ivs. It would have taken more time for me to walk to his house and ask him for access to his network.

Has anyone tried using two interfaces? I went from getting 30 ivs/sec to like 250 ivs/sec. My neighbor had a ten byte encryption key that only needed 20,000 ivs. It would have taken more time for me to walk to his house and ask him for access to his network.

I get 400/s typically, running aireplay with the arp replay attack on an AR5007EG on patched madwifi-ng drivers.

Ah, fucking fantastic :D So all you did was burn at a slower speed and airodump-ng stopped locking up the machine? Strange. What speed did you burn at by the way?

Yeah, it solved all of my problems. The slowest my program let me burn it at was 8x. I believe the problem copy was originally burned at like 24x. I would just burn it at the lowest speed possible... Better to wait a few minutes longer for it to burn than to wait a few hours longer trying to sort out your problems.