TrueCrypt, CipherShed, VeraCrypt
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 13.6k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
http://www.openwall.com/lists/john-dev/2015/12/31/1
It appears there are some fundamental differences in the forks of TrueCrypt. Specifically VeraCrypt appears to be doing key derivation in a "more secure" fashion than TC or CipherShed. Will the truecrypt2john and the code that cracks those volumes need to be changed?
https://forum.truecrypt.ch/t/veracrypt-or-ciphershed/449/10
Will that spawn a new format/tool, veracrypt2john --format=veracode ? I'll try to add some samples if I have some time today.
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 reviewing the existing truecrypt2john tool and the code that cracks TrueCrypt volumes, then compare the key-derivation differences described for TrueCrypt, CipherShed, and VeraCrypt. Use the linked discussion and any provided samples to determine whether the formats can share support or require a separate tool; done means the required scope and format handling are established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- cryptography, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100