As aanarchyy also said, it's just a zip file.
Have you tried with Bully 1.1? What kind of problems happened.
Printable View
To aanarchyy
Our associate C++ programmer wrote an additional mdk3 attack type. He was in contact with soxrok2212 on the matter and it might be posted on github not sure?
We can post the latest VMR-MDK script in raw format if you wish. If you wish to post it fine by us.
Reference Bully it did not function for us at all compared to Reaver. We embedded bully in varmacscan, it ran first then reaver ran against all targets seen. Bully did not function well in xterm windows. We then tried it from the command line. Against our targets reaver ran fine while bully did nothing.
We did these tests for over a month thinking we were doing something wrong. After a month we just gave up.
Again we will check the Bully version and retest. The test scripts are stored. You might give us your favorite bully command line to test again.
MTeams
as mmusket33, also in my area bully doesn't work. i believe it might be a lil too intrusive. all aps cracked with reaver +K 1, bully wasn't able to do it. the ap locks itself or even timeout on me while bully tries it's features. and another thing.. reaver reaches -70dbm and more maybe working a little slow(but it does), while bully tells that those(far away) aps are not in range or wps locked etc.
if bully gets a little too aggressive, then just increase the time per pin (it defaults to 0). And I've had bully work just fine for me even in the -80's whereas reaver can't even associate with AP's in the -40's. Obviously I'm talking about the version i made, not the one that comes with kali.
But to each their own, I prefer bully as it actually works on Openwrt and several other pieces of hardware that reaver fights with.
and mmusket33, why wouldn't you just make mdk3 it's own separate repo? It is a separate tool. ;-) Then just add in the readme that it requires that to be installed.
Just like how reaver says that it requires pixiewps to be installed to use the pixiedust attack.
I was hesitant to switch to Bully but I've found the same exact results. Distance is no longer a problem with Bully and everything runs much, much quicker.
Also, I do have the modified version of MDK3 if you'd like me to put it back on GitHub, though I didn't have any success with the extra modifications.
Bob, the other one is 3D modeling. The reason is, there are very talented ppl that already do an amazing job at coding and modeling, so I do not see why I should do that, ontop of doing everything else. So coding and modeling is a definite niope :)
To aanarchyy
When approaching WPS locked routers the processes must be automated due to the complex series of steps required to extract pins. Using keyboard output to the commandline is not practicable.
As you have written a bully version maybe you can tell us why bully does not function well when in an xterm window or when outputting to a file thru tee"
For example the following with reaver runs well however bully output to the screen and tee is intermittent and no pins are ever collected.
xterm -g 80x15-1+1 -T "bully" -e "bully wlan0mon -b 55:44:33:22:11:00 -c 1 -B --force -v 3 -L -d -s 00:11:22:33:44:55 2>&1 | tee logfile" &
It could be xterm but we got the same results when we tried the commandline thru a terminal window.
what results were you expecting and what results did you get?
running the command you just posted seemed to work just fine for me. All output ended up in "logfile" and posted in the xterm... bully went on as usual... (slightly altered)
http://postimg.org/image/h5ebomytz/
This would be far easier(and litter your thread less) if you and i could arrange some other means of communication...