Signature unmatched No hashed loaded.
#4
(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
Reply


Messages In This Thread
RE: Signature unmatched No hashed loaded. - by Snoopy - 03-22-2023, 06:22 PM