Printable View
I followed the tutorial on the airckack-ng site for cracking a WEP with no client. I got the password in hex. Tried to use it to log onto my dummy AP and Wicd says it is a bad password (made sure I set password to hex in Wicd). Since it is in hex I don't know if it's right or not. Can Aircrack return the wrong password? Or, is it a bug in Wicd? I was able to log onto my regular AP with Wicd and got no password error.
aircrack will check against the packet dump provided. did you remove the colons?
for example:
key: 1122334455Quote:
KEY FOUND! 100% Accuracy [11:22:33:44:55]
also make sure if you are copy/pasting that there is no white space before or after the key
you can try to connect via console:
Quote:
iwconfig <interface> essid <essid>
iwconfig <interface> key <key>
dhclient <interface>
Why don't you try cracking your regular AP ? Just set a temporary WEP key and crack it, then change it back.
This sounds like a mac adress filtering to me... Are you sure you're trying to crack your own dummy AP ?
comaX, you know what's funny ? Here in Holland the courthouse has decided it is NOT illegal to crack your neighbour's wifi !Quote:
Originally Posted by comaX
comaX, why would that sound like mac filtering? If that were the case he wouldn't have been able to inject packets in the first place without spoofing the correct mac, in which case he'd obviously know it.
We don't know where OP comes from though, and it's mostly illegal, prettu much everywhere...Quote:
Originally Posted by cgelici
Well, that sounds about right, even though I would need to check that*. He may have forgotten to spoof it when trying to connect afterwards...Quote:
Originally Posted by 5cardcharlie
And if it's not mac filtering, then it's just a bad password, or a bug. In either case, we would need more info about what is being done.
(I think the chop chop or fragmentation attack doesn't require you to be authed, and AP will respond anyway, mac filtering or not. I'm not sure though...)
In order to perform successful chop-chop attack you must do fake authentication
Maybe the fragmentation then. Once again, I don't remember !
OP seems to have disappeared, so I'll guess we'll know more when he comes back !
It is not so hard for firmware/driver programmers to implement custom routines in their code to protect AP against the aircrack attacks.Quote:
Maybe not the fragmentation then. Once again, I don't remember !
For example: to fight off fake authentication software procedure can simply refuse to authenticate and associate fake client when the real client is actively connected.