Quick tip: Veracrypt on a Raspberry Pi 2

As a long-year user of Truecrypt, whenever I set up a new system, Truecrypt has been among the first pieces of Software that I install. By the time I acquired the new Raspberry 2, I was willing to give Veracrypt a shot. It is one the follow-up projects for the discontinued Truecrypt. Here I will report on how I got it running.

My system was an up-to-date Raspbian. We need two additional dependencies, starting with

sudo apt-get install makeself

One also needs the FUSE library

sudo aptitude install libfuse-dev

You will have to download the Veracrypt sources as well as the sources of wxWidgets (although we build the CLI version only, it is still required to compile). Let’s assume you put them in

/home/pi/veracrypt/veracrypt_1.0f-1_Source.tar.bz2
/home/pi/wxwidgets/wxWidgets-3.0.2.tar.bz2

Now unpack the files

cd veracrpyt
bzip2 -d veracrypt_1.0f-1_Source.tar.bz2
tar xfv veracrypt_1.0f-1_Source.tar
cd
mkdir wxwidgets
cd wxwidgets
bzip2 -d wxWidgets-3.0.2.tar.bz2
tar xfv wxWidgets-3.0.2.tar

Now build Vera, which again takes a while… grab a coffee in the meantime.

cd /home/pi/vera/src/
make NOGUI=1 WX_ROOT=/home/pi/wxwidgets/wxWidgets-3.0.2/ wxbuild
make NOGUI=1 WXSTATIC=1
sudo cp Main/veracrypt /usr/local/bin/

A volume can be created interactively on the command line. Be patient, creating takes some time.

veracrypt --create -m=nokernelcrypto

Mounting works just as with Truecrypt,

sudo veracrypt container.tc /path/to/mount/ -m nokernelcrypto

but… it’s no fun within an Raspberry Pi. Mounting takes forever… maybe related to the higher count of iterations in the key derivation.

Advertisements

About goobypl5

pizza baker, autodidact, particle physicist
This entry was posted in Encryption, Security, Security/Encryption and tagged , . Bookmark the permalink.

6 Responses to Quick tip: Veracrypt on a Raspberry Pi 2

  1. Anonymous says:

    Got some error at the end of make NOGUI=1 WXSTATIC=1
    You know perhaps how i can fix this?
    make[1]: wx-config: Command not found
    make[1]: wx-config: Command not found
    Precompiling SystemPrecompiled.h
    SystemPrecompiled.h:13:19: fatal error: wx/wx.h: No such file or directory
    #include
    ^
    compilation terminated.
    /data/src/Build/Include/Makefile.inc:41: recipe for target ‘SystemPrecompiled.h.gch’ failed
    make[1]: *** [SystemPrecompiled.h.gch] Error 1
    Makefile:292: recipe for target ‘all’ failed
    make: *** [all] Error 2

    • goobypl5 says:

      It seems like the preprocessor can’t find the file wx/wx.h. One needs to take care of the the directory structure, such that the compiler knows where to find stuff. As far as I remember one really needs the “cd” commands that I posted, but I havn’t tried the build in some time. If you deviated from the program versions 1.0f-1/3.0.2, there may be some pitfalls as wel.

  2. Thomas D. says:

    Mounting didn’t work for me but all I needed was to open a simple, existing container. The “cryptsetup” command (LUKS) did the the trick in the end.

    * sudo cryptsetup open –type tcrypt /path/to/mycontainer.tc myMapperName
    * sudo mount /dev/mapper/myMapperName /media/myDevice

    * sudo umount /media/myDevice
    * sudo cryptsetup close myMapperName

  3. Sjoerd says:

    Could you please upload an updated description? I’d reallly like to use VeraCrypt on my Pi. Followed your steps but with a newer version of VeraCrypt (VeraCrypt_1.18_Source.tar.bz2). When I run “make NOGUI=1 WXSTATIC=1” I get the following output:

    Compiling Buffer.cpp
    g++: error: unrecognized command line option ‘-msse2’
    g++: error: unrecognized command line option ‘-maes’
    /home/pi/Downloads/Veracrypt/src/Build/Include/Makefile.inc:24: recipe for target ‘Buffer.o’ failed
    make[1]: *** [Buffer.o] Error 1
    Makefile:320: recipe for target ‘all’ failed
    make: *** [all] Error 2

    Any help would be very much appreciated! Thnx 🙂

  4. Pingback: Quick tip: Veracrypt on a Raspberry Pi 2 [update: Veracrypt 1.18] | randomgooby

Share your thoughts

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s