Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
Add VeraCrypt support #65
These patches implement support for VeraCrypt (https://veracrypt.codeplex.com), a fork of TrueCrypt.
The first patch corrects the encoding of the minimum version field in the volume header.
VeraCrypt documentation that is derived from TrueCrypt one (without the mistakes): https://veracrypt.codeplex.com/documentation
Differences between VeraCrypt and TrueCrypt : https://veracrypt.codeplex.com/discussions/569777#PostContent_1313325
bump version number to make it easy to separate versions with VeraCrypt support and those without. Remove several compilation warnings.
fix a build issue when trying to compile while "DEBUG" variable is set by adding a missing comma
Upstream seems to no longer care about it but it lives on with zuluCrypt where all these patches are already in.
tc-play in zuluCrypt for example can create and unlock VeraCrypt volumes that use a PIM value.This ability is not among patches above.
As someone currently evaluating cross-platform disk encryption options, I'd really like to see VeraCrypt support in tcplay. Not least because the TrueCrypt Security Assessment specifically calls out the weak volume header key derivation "iteration count is too small to prevent password guessing attacks for even moderately complex passwords" which is addressed by VeraCrypt.
Perhaps now that a few more years have passed, the other TrueCrypt forks are dead or stagnant, VeraCrypt has undergone its own security audit, and VeraCrypt support has been added to cryptsetup and other similar tools, it's worth re-evaluating the merits of including support for VeraCrypt?
If this PR in its current form is not acceptable, is there any form which would be accepted?