veracrypt / VeraCrypt
git clone https://github.com/veracrypt/VeraCrypt.git
VeraCrypt_1.26.29 · 4mo ago
Disk encryption with strong security based on TrueCrypt
+11
stars, 24h · #1,317
+~77
stars, 7 days · #1,643
+~330
stars, 30 days · #1,597
12k
★ total · +1% this week
1.4k
forks · 488 open issues
Star history (as recorded here)
LanguageC
License—
Created2014-11-08 (11y ago)
Last pushtoday
Watchers238
OwnerOrganization
GitHub topics
Links
- GitHub: github.com/veracrypt/VeraCrypt
- Homepage: https://veracrypt.jp
- Releases · Issues · Hacker News mentions
README excerpt
This archive contains the source code of VeraCrypt. It is based on the original TrueCrypt 7.1a with security enhancements and modifications. # Important You may use the source code contained in this archive only if you accept and agree to the license terms contained in the file 'License.txt', which is included in this archive. Note that the license specifies, for example, that a derived work must not be called 'TrueCrypt' or 'VeraCrypt' # Contents I. Windows II. Linux and Mac OS X III. FreeBSD and OpenBSD IV. Third-Party Developers (Contributors) V. Legal Information VI. Further Information # I. Windows ## Requirements for Building VeraCrypt for Windows: A detailed guide on how to build VeraCrypt on Windows can be found in the documentation in the repository and it is also available online or on the mirror. IMPORTANT: The 64-bit editions of Windows Vista and later versions of Windows, and in some cases (e.g. playback of HD DVD content) also the 32-bit editions do not allow the VeraCrypt driver to run without an appropriate digital signature. Therefore, all .sys files in official VeraCrypt binary packages are digitally signed with the digital certificate of the IDRIX, which was issued by GlobalSign certification authority. At the end of each official .exe and .sys file, there are embedded digital signatures and all related certificates (i.e. all certificates in the relevant certification chain, such as the certification authority certificates, CA-MS cross-certificate, and the IDRIX certificate). Keep this in mind if you compile VeraCrypt and compare your binaries with the official binaries. If your binaries are unsigned, the sizes of the official binaries will usually be approximately 10 KiB greater than the sizes of your binaries (there may be further differences if you use a different version of the compiler, or if you install a different or no service pack for Visual Studio, or different hotfixes for it, or if you use different versions of the required SDKs). ## Instructions for Signing and Packaging VeraCrypt for Windows: First, create an environment variable 'WSDK81' pointing to the Windows SDK for Windows 8.1 installation directory. The folder "Signing" contains a batch file (sign.bat) that will sign all VeraCrypt components using a code signing certificate present on the certificate store and build the final installation setup and MSI package. The batch file assumes that the code signing certificate is issued by GlobalSign. This is the case for IDRIX's certificate. If yours is issued by another CA, then you should put its intermediate certificates in the "Signing" folder and modify sign.bat accordingly. To generate MSI packages, WiX Toolset v3.11 must be installed. ## VeraCrypt EFI Boot Loader: VeraCrypt source code contains pre-built EFI binaries under src\Boot\EFI. The source code of VeraCrypt EFI Boot Loader is licensed under LGPL and it is available at https://github.com/veracrypt/VeraCrypt-DCS. For build instructions, please refer to t