You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Keyspace program from hashcat-utils gives different results than hashcat itself.
Tested on hashcat 3.6.0, I expect it to be even worse in newer versions of hashcat.
Example:
hashcat64.exe -m 13600 ?l?l?l?l?l?l?l?d?d --keyspace -a 3
30891577600
keyspace.exe -m 13600 ?l?l?l?l?l?l?l?d?d
45697600
The text was updated successfully, but these errors were encountered:
Hi, I just wanted to ask if there is an ETA for updated keyspace program so hashcat-keyspace could be computed easily, without OpenCL/GPU drivers present. Is it planned together with next versions of hashcat or is this bug of no importance for now?
I think I'll remove the keyspace tool from hashcat-utils as hashcat has --keyspace now. This way there's no need to maintain two different tools to provide the same functionality and to keep them in sync. Anyway, you do not need a GPU to run hashcat, just install the intel opencl runtime, it will work for almost all CPU (even AMD).
As brought up in this thread: https://hashcat.net/forum/thread-7437.html
Keyspace program from hashcat-utils gives different results than hashcat itself.
Tested on hashcat 3.6.0, I expect it to be even worse in newer versions of hashcat.
Example:
The text was updated successfully, but these errors were encountered: