+- 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: old zip file vs Nvidia (/thread-13657.html)
old zip file vs Nvidia - MFC - 07-14-2026
Hello,
This is my first post here, thank you for reading.
I have an old zip file to crack, it is from 2001 but may be from 2003 as the file inside is from 2003
Hascat wont run on it, it keeps giving me "Separator unmatched" or "No hashes loaded" or " Token length exception"
When I tried to use version 5 or 6 I got this
"Unknown hash-type '17200' selected"
I tried everything already, too many to list here, all ideas and commands google AI gave me I did
Is there a way to make a hash from this old file that will work on version 7.1.2 and my Nvidia GTX 1650?
Thanks
RE: old zip file vs Nvidia - drsnooker - 07-14-2026
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.
RE: old zip file vs Nvidia - MFC - 07-14-2026
(Today, 03:48 AM)drsnooker Wrote: 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.
Thank you