There are now official downloads for recent versions of Ubuntu provided by VeraCrypt. Please use those instead!
It's best to always check the VeraCrypt official downloads in case a more recent version has been released.
Download the resulting binary and applicable licenses (rendered from VeraCrypt_1.24-Update7 release).
It's also recommended that you verify your preferred checksum.
- GitHub: https://github.com/maresb/docker-build-veracrypt
- Docker Hub: https://hub.docker.com/repository/docker/maresb/docker-build-veracrypt
- VeraCrypt GitHub: https://github.com/veracrypt/VeraCrypt
- VeraCrypt official downloads: https://www.veracrypt.fr/en/Downloads.html
This Dockerfile is copyright © 2020 Ben Mares. (For details, see LICENSE.) It builds VeraCrypt from source code. I am in no way affiliated with VeraCrypt, IDRIX or wxWidgets.
By using this Dockerfile, you agree to the terms of the following licenses.
Veracrypt is copyright © 2013-2019 IDRIX, with contributions from several others. For details, see the VeraCrypt License.
VeraCrypt uses the wxWidgets library, which is copyright © 1998-2011 Julian Smart, Robert Roebling et al. For details, see the wxWindows Library License.
Since there is no official VeraCrypt binary for Ubuntu 20.04, users must either find a binary which they trust, or compile from source. Trust is a touchy subject when it comes to encryption software (see Motivation). Compiling from source is time-consuming and disk-consuming. But thanks to Docker, you can easily verify my build by reproducing it yourself.
When it comes to encryption software, it's difficult to be too careful. (For example, I'd recommend reading about both Crypto AG and the suspicious end of TrueCrypt.) Even for the official VeraCrypt downloads, there doesn't seem to be a good way to verify that those binaries actually correspond to the source code available on GitHub. I find it more reassuring to compile from publicly available source code. (Even if the source code is fine, that is no guarantee that the compiled binary is safe; for example, see "Reflections on Trusting Trust" by Ken Thompson.)
There is only one real subtlety to achieving a reproducible build for VeraCrypt. That is, that the wxWidgets 3.0 dependency uses the __DATE__ and __TIME__ preprocessor macros to store the compile time. Version 3.1.1 of wxWidgets introduced a reproducible build mode, however VeraCrypt is only compatible with 3.0. As a simple workaround, I replace all occurrences of __DATE__ and __TIME__ with a fixed value before preprocessing.
Note: Perhaps it's possible to compile VeraCrypt against some libwx package from Ubuntu? (I tried briefly but was unsuccessful.)
Complete either a) or b) below.
a) Either compile locally
Download Dockerfile and change to the corresponding directory.
git clone https://github.com/maresb/docker-build-veracrypt.git && cd docker-build-veracrypt
Then build VeraCrypt.
docker build -t build-veracrypt .
b) Or grab a premade image from Docker Hub
Pull the image from Docker Hub and retag:
docker pull maresb/docker-build-veracrypt
docker image tag maresb/docker-build-veracrypt build-veracrypt
docker rmi maresb/docker-build-veracrypt
id=$(docker create build-veracrypt)
docker cp $id:veracrypt .
docker cp $id:veracrypt_nogui .
docker cp $id:VeraCrypt_License.txt .
docker cp $id:wxWindows_Library_License.txt .
docker rm -v $id
docker rmi build-veracrypt
docker purge
If the image successfully builds, you can tag the build stage and look inside with
docker build -t build-veracrypt:build --target build .
docker run --rm -it build-veracrypt:build /bin/bash
Otherwise, in the output of a partial build, look for a line with an arrow directly followed by a hash such as
---> df7f92f1a162
Then you can look inside the image at the corresponding point with
docker run --rm -it df7f92f1a162 /bin/bash
In case you are missing any libraries, the following command should install them.
Normal version:
sudo apt-get install --no-install-recommends libfuse2 libgtk2.0-0 libsm6
No-GUI version:
sudo apt-get install --no-install-recommends libfuse2
By running VeraCrypt, you agree to the licenses.
You should now be able to run ./veracrypt, but you should
verify the checksums below.
You can install VeraCrypt with
sudo chmod a+x veracrypt
sudo mv veracrypt /usr/bin/veracrypt
To download and install the shortcut and icon,
sudo wget -O /usr/share/applications/veracrypt.desktop https://raw.githubusercontent.com/veracrypt/VeraCrypt/master/src/Setup/Linux/veracrypt.desktop
sudo wget -O /usr/share/pixmaps/veracrypt.xpm https://raw.githubusercontent.com/veracrypt/VeraCrypt/master/src/Resources/Icons/VeraCrypt-256x256.xpm
$ stat --printf="%s bytes\n" veracrypt
8046656 bytes
$ md5sum veracrypt
705c2c0cb9bc33e212c2a181eb91127f veracrypt
$ sha256sum veracrypt
e762fddc32ca9575a53be39699f3825b8c490704acba650a9b687c841e708305 veracrypt
$ b2sum veracrypt
b7ef803ee2c46a8ccbea96813a6e97b097aa7114c556b39c2c70f4e85e84786c5d8b9dbefaafc45a2e209f15d306e670ab1dc484c30b387f750a3a1e1d8ec2fd veracrypt
$ stat --printf="%s bytes\n" veracrypt_nogui
3228416 bytes
$ md5sum veracrypt_nogui
761981c7bb5c7c1b3d2faece7d01e50b veracrypt_nogui
$ sha256sum veracrypt_nogui
4cbf6245ee8f362fa438fcf4d88f116ce3db01be9783c6988c3d5c7b934be65f veracrypt_nogui
$ b2sum veracrypt_nogui
deb447b78fc859733ea5922f578d2b37617e850851c0eab9b8f7e5bcfebf974a9cb6b0d3cf887d9bcbefa1d9277bf129739763a74985b5b00c8aa6dd36c0f497 veracrypt_nogui