Signature unmatched No hashed loaded.

Signature unmatched No hashed loaded. - 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: Signature unmatched No hashed loaded. (/thread-11358.html)

Signature unmatched No hashed loaded. - boulevard - 03-22-2023

I have a file named test.zip, it's password is like "Cst.******", where * is 0-9,a-z,A-Z
My device is Tesla V100-32GB，my OS is Ubuntu 20.04LTS
First, I use

Code:
zip2john test.zip > temp.txt

, I got things like:

Code:
test.zip/test.pdf:$pkzip2$1*2*2*0*1a68...(many characters)...6030bc*$/pkzip2$:test.pdf:test.zip

Then, I store the

Code:
1*2*2*0*1a68...(many characters)...6030bc*

into a file named hash.txt
Then I use hashcat by command:

Code:
(base) ubuntu@VM-0-13-ubuntu:~/hashcat-6.2.6$ ./hashcat.bin -a 3 -m 17225 hash.txt Cst. -1 ?l?u?d -1 ?l?u?d -1 ?l?u?d -1 ?l?u?d -1 ?l?u?d -1 ?l?u?d

hashcat (v6.2.6) starting

txts/hash.txt: Byte Order Mark (BOM) was detected

clGetPlatformIDs(): CL_PLATFORM_NOT_FOUND_KHR

nvmlDeviceGetFanSpeed(): Not Supported

CUDA API (CUDA 11.4)

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

* Device #1: Tesla V100-SXM2-32GB, 32204/32510 MB, 80MCU

Minimum password length supported by kernel: 0

Maximum password length supported by kernel: 256

Hashfile 'hash.txt' on line 1 (1): Signature unmatched

No hashes loaded.

Started: Wed Mar 22 20:38:07 2023

Stopped: Wed Mar 22 20:38:08 2023

I think maybe test.zip file is not PKZIP (Mixed Multi-File), so I tried -m 17220, 17200, 17225, 17230, 17210, 20500, 20510, 23001, 23002, 23003, 13600

But all of them doesn't work.

What can I do to fix it?

RE: Signature unmatched No hashed loaded. - Snoopy - 03-22-2023

(03-22-2023, 02:46 PM)boulevard Wrote: hashcat (v6.2.6) starting

txts/hash.txt: Byte Order Mark (BOM) was detected

Hashfile 'hash.txt' on line 1 (1): Signature unmatched
No hashes loaded.

there are two things

first please store the hash.txt as file without this stupid BOM-Marker, plain ascii or utf-8 will be your friend

second, you removed the signature $pkzip2$ from the hash, this signature is needed so your hash.txt should look like this

$pkzip2$1*2*2*0*1a68...(many characters)...6030bc*$/pkzip2$

RE: Signature unmatched No hashed loaded. - boulevard - 03-22-2023

(03-22-2023, 04:16 PM)Snoopy Wrote:
(03-22-2023, 02:46 PM)boulevard Wrote: hashcat (v6.2.6) starting

txts/hash.txt: Byte Order Mark (BOM) was detected

Hashfile 'hash.txt' on line 1 (1): Signature unmatched
No hashes loaded.

there are two things

first please store the hash.txt as file without this stupid BOM-Marker, plain ascii or utf-8 will be your friend

second, you removed the signature $pkzip2$ from the hash, this signature is needed so your hash.txt should look like this

$pkzip2$1*2*2*0*1a68...(many characters)...6030bc*$/pkzip2$

Thank you a lot, now I restored this hash.txt with UTF-8 encoding, and added $pkzip2$ at the begin and end.

However, now new error occurs when I use -m 17200/17210/17220/17225:

Code:
Hashfile 'txts/hash.txt' on line 1 ($pkzip...2f498267e8c8287d6030bc*$/pkzip2$): Token length exception

* Token length exception: 1/1 hashes

  This error happens if the wrong hash type is specified, if the hashes are

  malformed, or if input is otherwise not as expected (for example, if the

  --username option is used but no username is present)

No hashes loaded.

and when I use -m 17230, the error info is:

Code:
Hashfile 'txts/hash.txt' on line 1 ($pkzip...2f498267e8c8287d6030bc*$/pkzip2$): Hash-value exception

No hashes loaded.

RE: Signature unmatched No hashed loaded. - Snoopy - 03-22-2023

(03-22-2023, 04:38 PM)boulevard Wrote:
(03-22-2023, 04:16 PM)Snoopy Wrote:
(03-22-2023, 02:46 PM)boulevard Wrote: hashcat (v6.2.6) starting

txts/hash.txt: Byte Order Mark (BOM) was detected

Hashfile 'hash.txt' on line 1 (1): Signature unmatched
No hashes loaded.

there are two things

first please store the hash.txt as file without this stupid BOM-Marker, plain ascii or utf-8 will be your friend

second, you removed the signature $pkzip2$ from the hash, this signature is needed so your hash.txt should look like this

$pkzip2$1*2*2*0*1a68...(many characters)...6030bc*$/pkzip2$

Thank you a lot, now I restored this hash.txt with UTF-8 encoding, and added $pkzip2$ at the begin and end.

However, now new error occurs when I use -m 17200/17210/17220/17225:

Code:
Hashfile 'txts/hash.txt' on line 1 ($pkzip...2f498267e8c8287d6030bc*$/pkzip2$): Token length exception * Token length exception: 1/1 hashes This error happens if the wrong hash type is specified, if the hashes are malformed, or if input is otherwise not as expected (for example, if the --username option is used but no username is present) No hashes loaded.

and when I use -m 17230, the error info is:

Code:
Hashfile 'txts/hash.txt' on line 1 ($pkzip...2f498267e8c8287d6030bc*$/pkzip2$): Hash-value exception No hashes loaded.

when you take a look at https://hashcat.net/wiki/doku.php?id=example_hashes you will see, that the only modes which complies with $pkzip2$1$ are 17200 and 17210

when both modes run into a "Token length exception" then your hash is to long and you have to try john the ripper for cracking