stop attack when nack code is SETUP_LOCKED

[feitoi]

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

[rofl0r]

wouldnt this lead to "quitting after 0 pin attempts" when using string pin ?

[feitoi]

advance_pin_count() is for to increment the index of p1 or p2 on normal attack.
I know that in string mode has protection of set_max_pin_attempts(1) implicit and also does not save .wpc file to avoid wrong.
To avoid any change in the index of p1 and/or p2 when using string pin, the use of if condition is good for it.

[feitoi]

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. (#274 (comment))
So I think it's better stop the attack.

[rofl0r]

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