Understanding integer overflow

Understanding integer overflow - Printable Version

+- hashcat Forum (https://hashcat.net/forum)
+-- Forum: Support (https://hashcat.net/forum/forum-3.html)
+--- Forum: hashcat (https://hashcat.net/forum/forum-45.html)
+--- Thread: Understanding integer overflow (/thread-6636.html)

Understanding integer overflow - nullcell - 06-13-2017

For the sake of argument let's assume I run the following attack with hashcat

Code:
hashcat64 -w 3 --restore-file-path=my.restore -o recovered.txt -m 2500 -a 3 --increment --increment-min=8 --increment-max=50 myrouter.hccapx ?a?a?a?a?a?a?a?a

When running the above, the attack starts as expected

If I execute the same command but change my min and max parameters to something like

Code:
hashcat64 -w 3 --restore-file-path=my.restore -o recovered.txt -m 2500 -a 3 --increment --increment-min=10 --increment-max=50 myrouter.hccapx ?a?a?a?a?a?a?a?a?a?a

I then recieve an integer overflow.

I guess my question is this, is hashcat only checking for integer overflow of the minimum length? Instead of all possible lengths? Is this by design and if so why? Wouldn't I receive an error with the first attack once it hit's a length of 10 as well?

RE: Understanding integer overflow - atom - 06-13-2017

No, hashcat is checking the overflow for every length, not just the minimum one. But it's checking the overflow whenever a new attack starts internally. If you use increment, each password length unfolds to such a new attack.