03-28-2016, 08:45 PM
According to the technical team at Passware, hashcat checks the ASCII string "TRUE" field during the decryption process. Passware and TC itself checks the CRC-32 checksum. In this case it seems like they differ.
I'll be happy to share the hash/password or some MB from the beginning of the disk with someone involved in development.
What are the odds of getting the ASCII string "TRUE" with a password/key that also makes sense?
In either way, I will reply to this thread when someone has shed some light over this strange issue.
I'll be happy to share the hash/password or some MB from the beginning of the disk with someone involved in development.
What are the odds of getting the ASCII string "TRUE" with a password/key that also makes sense?
In either way, I will reply to this thread when someone has shed some light over this strange issue.