Please note, this is a STATIC archive of website hashcat.net from October 2020, cach3.com does not collect or store any user information, there is no "phishing" involved.

hashcat Forum

Full Version: Separator unmatched when using example hash
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I'm running this command:
Code:
sudo ./hashcat64.bin -m 3200 -a 0 -p $ $2a$05$LhayLxezLhK1LhWvKxCyLOj0j1u.Kj0jZ0pEmm134uzrQlFvQJLF6 wordlists/realuniq.dict

Which is the example hash for bcrypt on https://hashcat.net/wiki/doku.php?id=example_hashes

When I run this I get the following error and it looks like something weird happened to the hash:
Code:
Hash 'a-bash5.Kj0jZ0pEmm134uzrQlFvQJLF6': Separator unmatched

No hashes loaded.

The same thing happens when I try the pbkdf2 sha256 example hash:
Code:
sudo ./hashcat64.bin -m 10000 -a 0 -p $ pbkdf2_sha256$20000$H0dPx8NeajVu$GiC4k5kqbbR9qWBlsRgDywNqC2vd9kqfk7zdorEnNas= wordlists/realuniq.dict

Code:
Hash 'pbkdf2_sha2560000=': Separator unmatched

No hashes loaded.

I then replaced the $ signs with : and stopped overwriting the default separator and got the same issue:
Code:
sudo ./hashcat64.bin -m 10000 -a 0 pbkdf2_sha256:20000:H0dPx8NeajVu:GiC4k5kqbbR9qWBlsRgDywNqC2vd9kqfk7zdorEnNas= wordlists/realuniq.dict

The hash in the error looks slightly better formed this time around but the error still exists:

Code:
Hash 'pbkdf2_sha256:20000:H0dPx8NeajVu:GiC4k5kqbbR9qWBlsRgDywNqC2vd9kqfk7zdorEnNas=': Separator unmatched

No hashes loaded.


This is obviously something simple I'm doing wrong, do I need to do any sort of sanitisation/re formatting of the hash before running it through hashcat?
Hashes containing '$' need to be enclosed in single quotes on the Unix commandline. This is because $[string] is a way to do variable substitution in bash and related shells.

Once you fix that, you won't need to specify the separator on the commandline.
(03-16-2019, 08:10 PM)royce Wrote: [ -> ]Hashes containing '$' need to be enclosed in single quotes  on the Unix commandline.

Once you do that, you also shouldn't need to specify the separator on the commandline.

Ah of course, thank you!