search

t6x / reaver-wps-fork-t6x

1.7k stars 405 forks source link

stop attack when nack code is SETUP_LOCKED #341

Closed feitoi closed 2 years ago

feitoi commented 3 years ago

I think it is more appropriate to use type int for the variable pin_count.

feitoi commented 3 years ago

Analyzing the nack codes, I saw that when a router starts WPS lock, the code is 0x000F, and if continue attacking with the -L option, NACK is returned just after M2 and the nack code is 0x000F. And also those routers that show are not with WPS lock, but it returns NACK soon after sending M2 and the nack code is also 0x000F. (https://github.com/t6x/reaver-wps-fork-t6x/issues/274#issuecomment-472952342) So I think it's better stop the attack.

rofl0r commented 2 years ago

oops, i totally forgot about this. but better late than never ;)