wifite2
wifite2 copied to clipboard
derv82
timeout on wps cracking
hey, i have an issue, after choosing the correct wps locked wifi using wifite 2... This is it ...
TP-Link_D932 (25db) WPS Pixie-Dust: [4m23s, PINs:1] Failed: More than 100 Timeouts
[+] TP-Link_D932 (25db) WPS Pixie-Dust: [4m23s, PINs:1] Failed
and so on timeouts and fails ... this is depressing!
I haven't seen an option where to change the timeout in the actual wifite program, unless you edit a script you may have to switch over to Reaver so you can fine tune that specific attack sir! The devs may have another idea though or if requested enough could choose to add a feature such as this into wifite!
i managed to crack the pin and the password twice after updating to wifite 2 , but suddenly and with nothing done , it's not working and every time i get a timeout and fail even if the wifi is in good range like the one above (25 db) . btw the same output for reaver, bully , pixiewps ... and i'm confused.. what did i do? maybe an update of kali caused that! so is there a solution for this?.. thanks for ur reply!
the same here 👎 dont crack wps pass huawei router 50db and anything else. (timeouts and fails)
Can you send a log or screenshot of the error that you're having issues with?
i managed to crack this 1 month ago ! but now it can't be easy thou, i don't get it... and i'm no linux expert!
@blmvxer what do you think is the problem, help please!
Do you have any logs? Maybe a copy of your dmesg while this is running also?
help me and guide how to get the logs and dmesg output? @blmvxer
I'll get back to you on logs, but during the issue go to a separate terminal and type sudo dmesg > dmesg.log
This could be other stuff. Remember, "pixiewps" hasn't been maintained for some time, "bully" is getting old and slow.. wifite2 is a little bit behind on those pull requests awaiting..
I figurd I fix it for myself, so I collected patches and did some work on "bully" may be seen over at https://github.com/kimocoder/bully
Then I collected patches from all over the place for wifite2 and did some myself.. the result is over at https://github.com/kimocoder/wifite2
Also changed from "reaver" to my "bully" fork seems to have fixed some issues / slow capturing and pixiewps stalling.
Take a look below
Enjoy :+1:
I have also a little timeout problem with 55+ db and I nevercracked a network. I think it also is scanning too slow, becauseI only get 3 Routers on every program, also airodump etc. My Laptop has over 20 Networks after a short time. But I can't crack with that. Fails... It's a Mac, so... Macs are not good for hacking
[+] analysis of captured handshake file: [+] tshark: .cap file contains a valid handshake for bc:05:43:77:68:e2 [+] cowpatty: .cap file contains a valid handshake for (FritzBox) [!] aircrack: .cap file does not contain a valid handshake WHAT?
This could be other stuff. Remember, "pixiewps" hasn't been maintained for some time, "bully" is getting old and slow.. wifite2 is a little bit behind on those pull requests awaiting..
I figurd I fix it for myself, so I collected patches and did some work on "bully" may be seen over at https://github.com/kimocoder/bully
Then I collected patches from all over the place for wifite2 and did some myself.. the result is over at https://github.com/kimocoder/wifite2
Also changed from "reaver" to my "bully" fork seems to have fixed some issues / slow capturing and pixiewps stalling.
Take a look below
Enjoy +1
Great work. +1
I can confirm it is considerably faster, even after years later.
Still failing after using your wifite @kimocoder