Truecrypt formats accepts "boot" and twofish variants but can't crack them
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 13.6k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
From http://hashcat.net/wiki/doku.php?id=example_hashes
These work:
http://hashcat.net/misc/example_hashes/hashcat_ripemd160_aes.tc
http://hashcat.net/misc/example_hashes/hashcat_sha512_aes.tc
http://hashcat.net/misc/example_hashes/hashcat_whirlpool_aes.tc
This doesn't work, I have no idea why.
http://hashcat.net/misc/example_hashes/hashcat_ripemd160_aes_boot.tc
These loads (we can't distinguish them from AES) but does not work:
http://hashcat.net/misc/example_hashes/hashcat_ripemd160_twofish_boot.tc
http://hashcat.net/misc/example_hashes/hashcat_ripemd160_twofish.tc
http://hashcat.net/misc/example_hashes/hashcat_sha512_twofish.tc
http://hashcat.net/misc/example_hashes/hashcat_whirlpool_twofish.tc
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with the linked TrueCrypt samples, comparing the working AES files with the boot and Twofish variants. Check how the example hashes are loaded and tested against those samples. Done means the listed boot and Twofish formats are correctly distinguished where needed and can crack their supplied passwords.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- cryptography, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100