Keyhunt still working for couple of days and 1676094623431730292326400 keys scanned which is more than 138% of range scanned.
how its possible? is there any bug?
Some things, remove -l compress it is complete ignored by the bsgs method
Second. READ the documentation:
https://github.com/albertobsd/keyhunt?tab=readme-ov-file#valid-n-and-maximun-k-values-for-specificIt clearly said:
If you exceed the max value of K the program can have a unknow behavior, the program can have a suboptimal performance, or in the wrong cases you can missing some hits and have an incorrect SPEED.
So increment your N value and adjust K according to that table