separator mismatch on old office hash 9720 - 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: separator mismatch on old office hash 9720 (/thread-9871.html) |
separator mismatch on old office hash 9720 - daryl178@cox.net - 02-10-2021 I'm getting a token length error on the following Excel hash: $oldoffice$0*c80c451496dc9459eb60d7bf73cdf4bb*b3487d522b7b724756fe6418d149b073*9d0f73f403c99a078bf8f7c7e7f5ba7b my commands have been: hashcat64.exe -m 9720 -a 3 --increment --increment-min 4 --show JulAugV2.hash ?a?a?a?a?a?a?a?a Mode 9720 matches the example hash. I compared the generated hashes from hashcat and JTR. I have also tried: hashcat64.exe -m 9710 -a 3 --increment --show JulAugV2.hash ?a?a?a?a?a?a?a?a but hashcat exits quietly (no messages). Here is the command output: y:\hashcat-5.1.0>hashcat64.exe -m 9720 -a 3 --increment --show JulAugV2.hash ?a?a?a?a?a?a?a?a Hashfile 'JulAugV2.hash' on line 1 ($oldof...9d0f73f403c99a078bf8f7c7e7f5ba7b): Separator unmatched No hashes loaded. y:\hashcat-5.1.0>type JulAugV2.hash $oldoffice$0*c80c451496dc9459eb60d7bf73cdf4bb*b3487d522b7b724756fe6418d149b073*9d0f73f403c99a078bf8f7c7e7f5ba7b y:\hashcat-5.1.0> I have tried version 6.1.1 with the same result. Does anyone have any corrections? RE: separator mismatch on old office hash 9720 - slyexe - 02-10-2021 The hash is 9710 and works fine on 6.1.1 on my system. Must be something wrong with your .hash file as there could be a break or space at the end of the hash. Otherwise, adding the hash thru cmd prompt works just dandy for myself. Code: hashcat.exe -m 9710 -d 2 -a 3 $oldoffice$0*cxxxxxxxxxxxx*9d0f73f403cxxxxxxxxxxxxxx7b ?a?a?a?a?a Code: Session..........: hashcat RE: separator mismatch on old office hash 9720 - daryl178@cox.net - 02-11-2021 (02-10-2021, 11:19 PM)slyexe Wrote: The hash is 9710 and works fine on 6.1.1 on my system. Must be something wrong with your .hash file as there could be a break or space at the end of the hash. Otherwise, adding the hash thru cmd prompt works just dandy for myself. Thank you slyexe. Specifying the hash on the commandline was a good pointer. I removed the line ending (0x0d0x0a) for this particular hash file and hashcat started working. Just like other hashes, I simply redirected straight from office2hashcat.py and didn't focus on the line ending. Since the file was old, I thought I had some ancient combination. I appreciate it. |