Today, 03:48 AM
Well it seems more and more people are trying to attack zip and rar files. Perhaps it is time for somebody in the hashcat community to finally deal with the long hashes that zip2john and rar2john return so that hashcat can run them...
The long hashes come because the hash extraction algo includes a copy of the (smallest) file in the archive. Until hashcat allows for those hashes, you got two choices.
1) just use John the ripper instead of hashcat
2) try various zip2hashcat (as found on github) to see if any one returns a short hash that hashcat can actually use.
(If successful with 2, please post a link to the best zip2hashcat, that you found)
Again, my usual comment is to try all this on a zip with a known password. So please create a new zip, and see if you can correctly recover the password before proceeding with the unknown archive.
The long hashes come because the hash extraction algo includes a copy of the (smallest) file in the archive. Until hashcat allows for those hashes, you got two choices.
1) just use John the ripper instead of hashcat
2) try various zip2hashcat (as found on github) to see if any one returns a short hash that hashcat can actually use.
(If successful with 2, please post a link to the best zip2hashcat, that you found)
Again, my usual comment is to try all this on a zip with a known password. So please create a new zip, and see if you can correctly recover the password before proceeding with the unknown archive.