Is there a way to make VeraCrypt work on the Raspberry Pi?

Topics: Technical Issues
Jan 15, 2015 at 8:16 PM
I’m able to install it on the Pi, but it won’t start and generates the error “cannot execute binary file,” supposedly because of the Pi’s ARM architecture CPU.
Jan 15, 2015 at 11:23 PM

VeraCrypt was not compiled for ARM and that's why it won't work.
If Fuse is available on Raspberry Pi (I think it's the case), then a simple recompile should provide a working binary (at least the console only version).
I don't have access to Raspberry Pi and I lack time for working on this, but I can offer my help to anyone willing to work on such port.
If you know any developer community for Raspberry Pi, you can forward this message to them.

Jan 15, 2015 at 11:57 PM
Thank you for your answer.

I’m new to the Pi myself and don’t belong to any community related to it, but considering its increasing popularity and the possibilities offered by VeraCrypt, it won’t be long before you are invited to help in making them compatible.
Feb 22, 2015 at 4:03 PM
There's now a build for the Raspberry Pi which has been compiled under Raspbian.

See thread:
Feb 25, 2015 at 10:20 PM
Thank you haggster for your efforts, I really appreciate your work.

I have create an installer using the binary you supplied and I uploaded it to the ARM contributions folder on Sourceforge:
I also updated the contributed resources section of VeraCrypt home page:

By the way, you can update your post above to put the direct link to your thread instead of the whole discussion:
Mar 7, 2015 at 11:21 AM

I wrote a how to article about VeraCrypt on the Raspberry Pi. You need ArchLinux ARM but i'm sure that it would be adaptable to other distributions.

I hope that it can help

Mar 7, 2015 at 2:41 PM
Merci Wared for writing the howto.

My only remark is that if would be better to add a step in the howto so that the users check that the source package has not been modified (for example by someone you may hack WordPress on the server). For that, you can put the PGP signature file at the same location and tell the users to download it alongside VeraCrypt official public key (either from or any trusted public key repository using ID=0x54DDD393) and then check the signature of the source package using this key.

These are extra steps but they are important for such security software and it is better to protect against any future server compromise.

I will also add your howto to the contributed resources section ( although I prefer to wait to have your feedback on my proposed modification.
Mar 7, 2015 at 9:14 PM
Thank you for your answer.

You are right, I'm going to add this step. But i get some problems with ArchLinux ARM, GnuPG and .asc file. It seems to work with .sig files. Do you have a .sig file ?

Thank you

Mar 7, 2015 at 10:15 PM
Yes, I always provide sig file. For the Linux sources (veracrypt_1.0f-1_Source.tar.bz2), the sig file is veracrypt_1.0f-1_Source.tar.bz2.sig. You can just download this sig file ( and then put it on your server on the same place as the source archive.
I propose the following steps:
gpg --with-fingerprint VeraCrypt_PGP_public_key.asc (Check that the displayed fingerprint is 993B7D7E8E413809828F0F29EB559C7C54DDD393)
gpg --import VeraCrypt_PGP_public_key.asc
gpg --verify veracrypt_1.0f-1_Source.tar.bz2.sig veracrypt_1.0f-1_Source.tar.bz2
voilà voilà...Thank you for your effort to help VeraCrypt users.
Mar 8, 2015 at 5:21 PM
Thank you for you help !

I have updated the howto.

Mar 8, 2015 at 8:53 PM
Perfect :-)
I have added your link to the contributed resources section.

Bonne soirée!