Separator Unmatched using Output Formats
#1
Question 
I'm puzzled as to why I cannot get the output-formats working and require assistance.

OS: Debian Buster
Hashcat Version: v6.2.5-21-g0bf0414dc

I get slightly different messages with a 5600 to a 1000 hash. (i have tried doing all the format types to test also 1 - 15)
Could someone give an example of the correct syntax please?


Using the examples hashes:

5600 Hash

$ cat 5600.hash
admin::N46iSNekpT:08ca45b7d7ea58ee:88dcbe4446168966a153a0064958dac6:5c7830315c7830310000000000000b45c67103d07d7b95acd12ffa11230e0000000052920b85f78d013c31cdb3b92f5d765c783030

$ cat 5600.hash.pot
ADMIN::N46iSNekpT:08ca45b7d7ea58ee:88dcbe4446168966a153a0064958dac6:5c7830315c7830310000000000000b45c67103d07d7b95acd12ffa11230e0000000052920b85f78d013c31cdb3b92f5d765c783030:hashcat

So I have confirmed I have cracked this example hash and can see it in the potfile as expected.

hashcat -m 5600 --potfile-path 5600.hash.pot --show  --username --outfile-format=2 5600.hash
Hashfile '5600.hash' on line 1 (admin:...85f78d013c31cdb3b92f5d765c783030): Separator unmatched
No hashes loaded.

Why am I getting this error with a 5600 hash?

----------------------------------------------------------------------------------------------------

If I do the same test with a NTLM 1000 hash

$ cat 1000.hash.pot
b4b9b02e6f09a9bd760f388b67351e2b:hashcat

$ cat 1000.hash
b4b9b02e6f09a9bd760f388b67351e2b

hashcat -m 1000 --potfile-path 1000.hash.pot --show  --username --outfile-format=2 1000.hash
Failed to parse hashes using the 'native hashcat' format.
No hashes loaded.
Reply
#2
In both of your examples you are using --username, which is not necessary because there is no username in front of the hash.
Redo your commands without it, and you'll be fine.

(The 'admin' username in the 5600-hash is actually needed and is in fact part of the hash.)
Reply
#3
(12-09-2021, 12:56 PM)Banaanhangwagen Wrote: In both of your examples you are using --username, which is not necessary because there is no username in front of the hash.
Redo your commands without it, and you'll be fine.

(The 'admin' username in the 5600-hash is actually needed and is in fact part of the hash.)

Thanks this certainly Solves the issue - i knew it would be something simple. Thanks :-)
Reply