It seems with your configuration this specific check triggers:
https://github.com/hashcat/hashcat/blob/...600.c#L591
so the data specified in the hash is smaller than the expected decrypted data. Which is kind of weird . Are you sure that 146985 is the right value and is present twice in your hash line ?
Not sure when this could happen. We might need to remove or change this check... but we also need to understand when this happens. Most probably when the compression made the raw data larger, instead of smaller !? So compression basically made it worse
can you verify that this is also where it fails for you by compiling hashcat with that check commented out ?
I have no clue what you mean with the "-O" check, I can't reproduce this problem here.
Does the benchmark work for you without errors (hashcat -m 11600 -b) ?
https://github.com/hashcat/hashcat/blob/...600.c#L591
so the data specified in the hash is smaller than the expected decrypted data. Which is kind of weird . Are you sure that 146985 is the right value and is present twice in your hash line ?
Not sure when this could happen. We might need to remove or change this check... but we also need to understand when this happens. Most probably when the compression made the raw data larger, instead of smaller !? So compression basically made it worse
can you verify that this is also where it fails for you by compiling hashcat with that check commented out ?
I have no clue what you mean with the "-O" check, I can't reproduce this problem here.
Does the benchmark work for you without errors (hashcat -m 11600 -b) ?