I ran into a couple of tricky issues
#1
1.
The hash of the ZIP file I need to crack is too long.I had to turn it into a text file.But how do I get hashcat to read the hash values in the text file?
I don't know how to convert a text file to a readable hash file.

2.I use a third party platform to help me.This way I can use the text file directly, but have another problem:

When hashcat runs, it prompts me:

Counted lines in H:\hashcat-6.2.5\hashcat-6.2.5\hsh.txt
                                           
H:\hashcat-6.2.5\hashcat-6.2.5>pause


Then it will automatically exit.

This confuses me.


Here is the complete process:

H:\hashcat-6.2.5\hashcat-6.2.5>hashcat.exe -a 3 --session=2022-08-13 -m 17225 -w 3 --remove -p : --hwmon-disable --outfile-format=1,2 -i --increment-min=10 --increment-max=10 -1 QWERTYUIOPASDFGHJKLZXCVBNM0123456789 "H:\hashcat-6.2.5\hashcat-6.2.5\hsh.txt" ?1?1?1?1?1?1?1?1?1?1

hashcat (v6.2.5) starting



Unsupported AMD HIP runtime version '0.0.3224' detected! Falling back to OpenCL...



CUDA API (CUDA 11.7)

====================

* Device #1: NVIDIA GeForce RTX 3060 Laptop GPU, 5151/6143 MB, 30MCU



OpenCL API (OpenCL 3.0 CUDA 11.7.101) - Platform #1 [NVIDIA Corporation]

========================================================================

* Device #2: NVIDIA GeForce RTX 3060 Laptop GPU, skipped



Minimum password length supported by kernel: 0

Maximum password length supported by kernel: 256



Counted lines in H:\hashcat-6.2.5\hashcat-6.2.5\hsh.txt

H:\hashcat-6.2.5\hashcat-6.2.5>pause


Text document with oversized hash, 15MB, I can't upload.
Reply
#2
I'm not sure what the exact issue is. But I'm wondering if a 10 char attack is too long for mode 17225.

Your attack could be done like this instead:

H:\hashcat-6.2.5\hashcat-6.2.5>hashcat.exe -a 3 --session=2022-08-13 -m 17225 -w 3 --remove --hwmon-disable -1 ?u?d "H:\hashcat-6.2.5\hashcat-6.2.5\hsh.txt" ?1?1?1?1?1?1?1?1?1?1

I'm not sure if you might need to set a -o for an output file, if you also set --outfile-format, but under all circumstances --outfile-format 1,2 and -p : are the default settings, so they're not needed.
Reply
#3
26+10 = 36, lenght of 10 36^10 should be attackable as this is lower than 2^64 (the maximum candidates hashcat can store before running into overflow)

i dont get why the hsh.txt is given by full path if its already inside your hahscat folder you can simply use hsh.txt

BUT a 15mb hash is quite huge, i think the mainproblem will be, that there are some lenght restrictions apply here, how do you obtain the hash0? there is a python script from john the ripper, all you need to do is redirect the output directly t a text file like

zip2john.py zipfile > hash.txt
Reply