-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does not work with newer versions of hashcat #54
Comments
could you be more specific what doesn't work? |
hashtopus.exe log with debug flag "true":
Run by hand:
Remove hash list filename from arguments (not needed on calculating keyspace or speed)
And it seems, are not checked hashcat exit codes in the calculation speed and keyspace. |
hmm, looks like it. but the syntax doesn't seem wrong compared to what the help prints... is it possible that some of the parameters were removed from hashcat? like --quiet or --keyspace or something? |
Watched the parsing parameters in the new versions of hashcat. All parameters are the same, but stricter rules in the parsing. The first should be only options with a "-" or "--". Further parameters depend on the mode:
|
i dont understand. you need to specify attack type and hash type with --keyspace as well.... about the - or --, does that mean i can only use ALL - or ALL -- but not mix them together? |
Ok, for simpler. |
OOOOOOHHH! Now I understand. I thought you needed hash/hashfile/mask for --keyspace but I guess you really don't. I will fix this. |
Watch out there is a slight issue with hashcat when dealing with WPA (--hash-type=2500) and --keyspace it requires a hccap file which we assume is a bug. As well as --keyspace reporting differently for the exact same task depending on --hash-type specified Edit: --keyspace is reporting correctly for each hash-type specified just confirmed with atom, the WPA issues is a bug and will be fixed soon. |
thanks for the heads-up. so i will just wait for the fix and then drop the #HL# completely for --keyspace |
Any news on this? |
oh man, i havent cracked a hash in a long time, i guess i will fix this when i need it again... |
From version 3.20 hashcat has strong requirements for the order and composition parameters. Agents don't work properly.
Version 3.30 adds new exit codes, perhaps it is important to.
The text was updated successfully, but these errors were encountered: