-m 11600 7z - 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: -m 11600 7z (/thread-6744.html) |
-m 11600 7z - gorilla.bas - 07-31-2017 Hello all, Today i tried hashcat, and it shredded my VC container very nicely But when trying a .7z i struck an issue, i cannot crack it even though i know the password. tools win x 64b cmd|color C 7z2hashcat (7z2hashcat64-1.1.exe) hashcat (hashcat-3.6.0+274.7z) 7z v 9.20 Extract hash with "7z2hashcat.exe myarch.7z >>hash" Create dictionary with the password insde dic.k (i use letters as .revisions) "hashcat64.exe -m 11600 hash dic.k" Code: Session..........: hashcat no success. myarch.7z is then manually extracted with the same password successfully. sometimes i crack myself up... RE: -m 11600 7z - philsmd - 08-01-2017 Difficult to say without having the .7z and the extracted hash (but you are right, it is not allowed to post hashes here according to the forum's rules). I would say that it makes sense in this case to test if the example hash cracks (https://hashcat.net/wiki/example_hashes). Furthermore, it is not always recommended to use the beta versions to report problems. Maybe you could try the latest release version of hashcat too (https://hashcat.net/hashcat) ? RE: -m 11600 7z - gorilla.bas - 08-01-2017 Hello! I googled around and found a post stating i should try the beta, when cracking 7z. Anyways, new test today, with a much smaler passphrase. And it worked. Is there perhaps a max length on passphrases? RE: -m 11600 7z - philsmd - 08-02-2017 Yeah, you are right it sometimes depends on how "experimental" the beta currently is. Sometimes (actually very often) betas contain fixes for known problems/bugs and therefore at that very moment we recommend to use betas such that the user doesn't experience the problem (and the user can confirm that the beta version fixed the problem). Other times, the betas are (very) experimental (like it is currently the case, since there were a lot of changes involving changes of max supported pass and salt length etc, see the github commit history for details). There are some maximal values for passwords (also mentioned here: https://hashcat.net/wiki/doku.php?id=frequently_asked_questions#what_is_the_maximum_supported_password_length). In general, you should see within the status display if the password candidate was too long (have a look at the line labeled "Rejected"). You didn't really answer the question about if older and/or the current release version was able to crack your hash. You also didn't mention if the example hash works for you. |