VMR-MDK-K2-011x8.sh for Kali2.0

[mmusket33]

To wmxuser:

Thank you for your input.


MTeams has found that even the same make of router by mac code can react differently to the VMR-MDK series. This is why we have never ask for nor published a list of routers which are susceptible to the VMR-MDK approach. The only way to know if WPS pins can be obtained is to test that specific WPS Locked router for a few days.

Furthermore we have cracked WPS locked routers which when locked did not give up pins BUT during the VMR-MDK process, the router opened and the pin reset to 12345670 resulting in an extraction of the WPA Key.

So our rule is to test each specific router for the vulnerability and ignore the make and model.

MTeams

[tridyman]

To wmxuser:

Thank you for your input.


MTeams has found that even the same make of router by mac code can react differently to the VMR-MDK series. This is why we have never ask for nor published a list of routers which are susceptible to the VMR-MDK approach. The only way to know if WPS pins can be obtained is to test that specific WPS Locked router for a few days.

Furthermore we have cracked WPS locked routers which when locked did not give up pins BUT during the VMR-MDK process, the router opened and the pin reset to 12345670 resulting in an extraction of the WPA Key.

So our rule is to test each specific router for the vulnerability and ignore the make and model.

MTeams

I admire the work done and time consuming for a personal satisfaction or therapy, but as a constructive criticism I believe that recently +/-
a lot of new process are just the pretty much the same dog with different collar. Just my 2cent, but let's keep testing and enjoy the time and keep watching when process runs and the uploads at our side network. Happy testing,