{{Move|VeraCrypt|VeraCrypt is the maintained fork.|section=VeraCrypt article}}

−

{{Article summary heading|Related}}

−

{{Article summary wiki|Disk Encryption}}

−

{{Article summary wiki|Tcplay}}

−

{{Article summary end}}

−

'''TrueCrypt''' is a free open source on-the-fly encryption (OTFE) program. Some of its features are:

+

{{Related articles start}}

+

{{Related|Disk encryption}}

+

{{Related|Tcplay}}

+

{{Related|Tomb}}

+

{{Related articles end}}

+

+

{{Warning|Development of TrueCrypt was discontinued on May 2014, i.e. it [http://truecrypt.sourceforge.net/ will no longer receive updates and fixes]. The final release repository with information about TrueCrypt code audit is found at [https://www.grc.com/misc/truecrypt/truecrypt.htm].

+

+

Consider using [https://veracrypt.fr/ VeraCrypt], a TrueCrypt fork in active development installable with the {{Pkg|veracrypt}} package; VeraCrypt storage format is compatible with TrueCrypt storage format since version 1.0f.

+

}}

+

+

{{Warning|On 2015/09/26 two critical security issues has been found in '''Windows''' version of TrueCrypt: CVE-2015-7358 and CVE-2015-7359. Take this into account if you're planning to use this software to share encrypted volumes between Windows and ArchLinux. More information: [https://veracrypt.codeplex.com/SourceControl/changeset/cf4794372e5dea753b6310f1ca6912c6bfa86d45 1][http://www.theregister.co.uk/2015/09/29/google_flaks_find_admin_elevation_holes_that_gave_truecrypt_audit_the_slip/ 2]}}

+

+

{{Note|1={{Pkg|truecrypt}} 1:7.1a-3 and {{Pkg|veracrypt}} 1.16-5 cannot mount volumes since the [https://www.archlinux.org/news/c-abi-change/ C++ ABI change] on 2015-12-10, see {{Bug|47325}} and the [https://bbs.archlinux.org/viewtopic.php?id=206047 forum thread]. [[Downgrading]] to ''truecrypt'' 1:7.1a-2 works around the problem. Furthermore, the problem appears to be fixed in 1:7.1a-4.}}

+

+

TrueCrypt is a free open source on-the-fly encryption (OTFE) program. Some of its features are:

* Virtual encrypted disks within files that can be mounted as real disks.

* Virtual encrypted disks within files that can be mounted as real disks.

* Encryption of an entire hard disk partition or a storage device/medium.

* Encryption of an entire hard disk partition or a storage device/medium.

Line 15:

Line 26:

* "Hidden volumes" within a normal "outer" encrypted volume. A hidden volume can not be distinguished from random data without access to a passphrase and/or keyfile.

* "Hidden volumes" within a normal "outer" encrypted volume. A hidden volume can not be distinguished from random data without access to a passphrase and/or keyfile.

−

For more details on how TrueCrypt compares to other disk encryption solution, see [[Disk Encryption#Comparison table]].

+

For more details on how TrueCrypt compares to other disk encryption solution, see [[Disk encryption#Comparison table]].

== Installation ==

== Installation ==

−

Type as root in a terminal:

+

−

# pacman -S truecrypt

+

{{Note|For opening and accessing an existing TrueCrypt container [[#Accessing a TrueCrypt container using cryptsetup|cryptsetup]] is the preferred way, since it is well integrated with the rest of the system. Creating a new TrueCrypt container can be done using {{ic|truecrypt}}, after which it can be opened using {{ic|cryptsetup}}.}}

+

+

[[Install]] {{Pkg|truecrypt}} from the [[official repositories]].

If you use any kernel other than {{Pkg|linux}} install the corresponding kernel module.

If you use any kernel other than {{Pkg|linux}} install the corresponding kernel module.

−

If you are using truecrypt to encrypt a virtual filesystem (e.g. a file), the module will be automatically loaded whenever you run the {{ic|truecrypt}} command. Add it to the MODULES array in /etc/rc.conf.

+

If you are using truecrypt to encrypt a virtual filesystem (e.g. a file), the module will be automatically loaded whenever you run the ''truecrypt'' command.

If you are using truecrypt to encrypt a physical device (e.g. a hard disk or usb drive), you will likely want to load the module during the boot sequence:

If you are using truecrypt to encrypt a physical device (e.g. a hard disk or usb drive), you will likely want to load the module during the boot sequence:

−

Add the module to /etc/modules-load.d/:

+

Add the module to {{ic|/etc/modules-load.d/}}:

# tee /etc/modules-load.d/truecrypt.conf <<< "truecrypt"

# tee /etc/modules-load.d/truecrypt.conf <<< "truecrypt"

−

{{Note | It does not appear that loading a module applies with TrueCrypt 7.0a, the current version in Arch as of 4/19/2011. The above advice may be outdated with respect to the module, however it is still important to enable {{ic|fuse}}, {{ic|loop}} and your encryption algorithm (e.g. {{ic|AES}}, {{ic|XTS}}, {{ic|SHA512}}) in custom kernels.

+

{{Note|

−

If you only want to open and access an existing truecrypt container, this can also be done with {{ic|cryptsetup}} i.e. without installing Truecrypt.}}

+

* This didn't work for me (module truecrypt seems to be non-existent now), but adding "loop" module worked

+

# tee /etc/modules-load.d/truecrypt.conf <<< "loop"

+

# modprobe loop

+

* It does not appear that loading a module applies with TrueCrypt 7.1a, the current version in Arch as of 4/19/2013. The above advice may be outdated with respect to the module, however it is still important to enable '''FUSE''', '''loop''' and your encryption algorithm (e.g. '''AES''', '''XTS''', '''SHA512''') in custom kernels.

+

If you only want to open and access an existing truecrypt container, this can also be done with {{ic|cryptsetup}} i.e. without installing Truecrypt.

+

}}

+

+

== Accessing a TrueCrypt or VeraCrypt container using cryptsetup ==

+

+

Since version 1.6.7, {{Pkg|cryptsetup}} supports opening TrueCrypt and VeraCrypt containers natively, without the need of the {{Pkg|truecrypt}} or {{Pkg|veracrypt}} package. Use the following command as a guideline.

+

$ cryptsetup --type tcrypt open container-to-mount container-name

+

+

To mount a VeraCrypt cointainer, you must use the {{ic|--veracrypt}} option alongside {{ic|--type tcrypt}}. If using a custom Personal Iteration Multiplier (PIM), use the {{ic|--veracrypt-query-pim}} option to be promoted for the PIM.

+

+

Replace {{ic|container-to-mount}} with the device file under {{ic|/dev}} or the path to the file you wish to open. Upon successful opening, the plaintext device will appear as {{ic|/dev/mapper/container-name}}, which you can {{ic|mount}} like any normal device.

+

+

If you are using key files, supply them using the {{ic|--key-file}} option, to open a hidden volume, supply the {{ic|--tcrypt-hidden}} option and for a partition or whole drive that is encrypted in system mode use the {{ic|--tcrypt-system}} option.

+

+

See {{man|8|cryptsetup}} for more details and all supported options.

+

+

=== Automounting using /etc/crypttab ===

+

+

Since version 206, [[systemd]] supports (auto)mounting TrueCrypt containers at boot or runtime using {{ic|/etc/crypttab}}.

+

+

The following example setup will mount {{ic|/dev/sda2}} in system encryption mode as soon as {{ic|/mnt/truecrypt-volume}} is accessed using systemd's automounting logic. The passphrase to open the volume is given in {{ic|/etc/volume.password}}. Note that the device file given in {{ic|/etc/fstab}} needs to be the one from {{ic|/dev/mapper/}} and not, for example, from {{ic|/dev/disk/by-uuid/}} for automounting logic to kick in. Other than that you can still reliably identify the encrypted volume itself inside of {{ic|/etc/crypttab}} using device file names from {{ic|/dev/disk/}}.

Instead of ''auto'', you can put directly your filesystem, and put usual mount options. It is useful with NTFS for mounting as a normal user.

+

+

See {{man|5|crypttab}} for more details and options supported.

== Encrypting a file as a virtual volume ==

== Encrypting a file as a virtual volume ==

+

The following instructions will create a file that will act as a virtual filesystem, allowing you to mount it and store files within the encrypted file. This is a convenient way to store sensitive information, such as financial data or passwords, in a single file that can be accessed from Linux, Windows, or Macs.

The following instructions will create a file that will act as a virtual filesystem, allowing you to mount it and store files within the encrypted file. This is a convenient way to store sensitive information, such as financial data or passwords, in a single file that can be accessed from Linux, Windows, or Macs.

To create a new truecrypt file interactively, type the following in a terminal:

To create a new truecrypt file interactively, type the following in a terminal:

−

$ truecrypt -c

+

$ truecrypt -t -c

−

−

{{Box Note | This command will not work in newer version of truecrypt. Type "truecrypt" instead and manage your encrypted volumes from the GUI or specify the necessary options to work in the command line. (truecrypt -h)}}

Follow the instructions, choosing the default values unless you know what you are doing:

Follow the instructions, choosing the default values unless you know what you are doing:

Line 47:

Line 97:

Select [1]: 1

Select [1]: 1

−

Enter file or device path for new volume: /home/user/myEncryptedFile.tc

+

Enter file or device path for new volume: /home/user/''EncryptedFile''.tc

'''''Note:''' Truecrypt requires root privileges and as such, running the above command as a user will attempt to use ''{{Ic|sudo}}'' for authentication. To work with files as a regular user, please see the appropriate section below.

+

{{Note|Truecrypt requires root privileges and as such, running the above command as a user will attempt to use '''sudo''' for authentication. To work with files as a regular user, please see[[#Mount volumes as a normal user|Mount volumes as a normal user]].}}

Once mounted, you can copy or create new files within the encrypted directory as if it was any normal directory. When you are you ready to re-encrypt the contents and unmount the directory, run:

Once mounted, you can copy or create new files within the encrypted directory as if it was any normal directory. When you are you ready to re-encrypt the contents and unmount the directory, run:

−

$ truecrypt -d

+

$ truecrypt -t -d

−

Again, this will require administrator privileges through the use of {{Ic|sudo}}. After running it check if the files that are to be encrypted are indeed no longer in the directory. (might want to try unimportant data first) If they are still there, note that {{ic|rm}} doesn't make the data unrecoverable.

+

Again, this will require administrator privileges through the use of '''sudo'''. After running it check if the files that are to be encrypted are indeed no longer in the directory. (might want to try unimportant data first) If they are still there, note that ''rm'' doesn't make the data unrecoverable.

For more information about truecrypt in general, run:

For more information about truecrypt in general, run:

−

$ man truecrypt #Note: as of 1:7.1a-1 dont see a man or info page

+

$ man truecrypt

+

{{Note|As of 1:7.1a-1 dont see a man or info page.}}

Several options can be passed at the command line, making automated access and creation a simple task. The man page is highly recommended reading.

Several options can be passed at the command line, making automated access and creation a simple task. The man page is highly recommended reading.

== Encrypting a physical volume ==

== Encrypting a physical volume ==

+

+

{{Note|1= If you are having problems with the graphical interface, you can run in CLI mode with the -t flag.}}

+

If you want to use a keyfile, create one with this command:

If you want to use a keyfile, create one with this command:

−

truecrypt --create-keyfile /etc/disk.key

+

truecrypt --create-keyfile /etc/disk.key

By default both passphrase and key will be needed to unlock the volume.

By default both passphrase and key will be needed to unlock the volume.

−

Create a new volume in the device /dev/sda1:

+

Create a new volume in the device {{ic|/dev/sda1}}:

−

truecrypt --volume-type normal -c /dev/sda1

+

# truecrypt --volume-type=normal -c /dev/sda1

−

Map the volume to /dev/mapper/truecrypt1:

+

Map the volume to {{ic|/dev/mapper/truecrypt1}}:

−

truecrypt -N 1 /dev/sda1

+

# truecrypt -N 1 /dev/sda1

If this command does not for you try this to map the volume:

If this command does not for you try this to map the volume:

−

truecrypt --filesystem=none --slot=1 /dev/sda1

+

# truecrypt --filesystem=none --slot=1 /dev/sda1

−

If you want to use another file system than ext3 simply format the disk like you normally would, except use the path /dev/mapper/truecrypt1.

+

Simply format the disk like you normally would choosing your favourite [[file system]], except use the path {{ic|/dev/mapper/truecrypt1}}. E.g. for ext4 use:

−

mkfs.ext3 /dev/mapper/truecrypt1

+

# mkfs.ext4 /dev/mapper/truecrypt1

Mount the volume:

Mount the volume:

−

mount /dev/mapper/truecrypt1 /media/disk

+

# mount /dev/mapper/truecrypt1 /media/disk

Map and mount a volume:

Map and mount a volume:

−

truecrypt /dev/sda1 /media/disk

+

# truecrypt /dev/sda1 /media/disk

Unmount and unmap a volume:

Unmount and unmap a volume:

−

truecrypt -d /dev/sda1

+

# truecrypt -d /dev/sda1

== Creating a hidden volume ==

== Creating a hidden volume ==

−

First, create a normal outer volume as described above.

−

Map the outer volume to /dev/mapper/truecrypt1:

+

First, create a normal outer volume as described in [[#Encrypting a physical volume]].

−

truecrypt -N 1 /dev/sda1

+

+

Map the outer volume to {{ic|/dev/mapper/truecrypt1}}:

+

# truecrypt -N 1 /dev/sda1

Create a hidden truecrypt volume in the free space of the outer volume:

Create a hidden truecrypt volume in the free space of the outer volume:

−

truecrypt --type hidden -c /dev/sda1

+

# truecrypt --type hidden -c /dev/sda1

You need to use another passphrase and/or keyfile here than the one you used for the outer volume.

You need to use another passphrase and/or keyfile here than the one you used for the outer volume.

Unmap the outer truecrypt volume and map the hidden one:

Unmap the outer truecrypt volume and map the hidden one:

−

truecrypt -d /dev/sda1

+

# truecrypt -d /dev/sda1

−

truecrypt -N 1 /dev/sda1

+

# truecrypt -N 1 /dev/sda1

Just use the passphrase you chose for the hidden volume and TrueCrypt will automatically choose it before the outer.

Just use the passphrase you chose for the hidden volume and TrueCrypt will automatically choose it before the outer.

Create a file system on it (if you have not already) and mount it:

Create a file system on it (if you have not already) and mount it:

−

mkfs.ext3 /dev/mapper/truecrypt1

+

# mkfs.ext4 /dev/mapper/truecrypt1

−

mount /dev/mapper/truecrypt1 /media/disk

+

# mount /dev/mapper/truecrypt1 /media/disk

Map and mount the outer volume with the hidden write-protected:

Map and mount the outer volume with the hidden write-protected:

−

truecrypt -P /dev/sda1 /media/disk

+

truecrypt -P /dev/sda1 /media/disk

+

+

== Mount a special filesystem ==

−

==Mount a special filesystem==

+

{{Note|Current Versions of truecrypt seem to support NTFS write support by default so the {{ic|--filesystem}} flag no longer seems to be necessary.}}

−

{{Box Note | Current Versions of truecrypt seem to support ntfs write support by default so the {{ic|--filesystem}} flag no longer seems to be necessary.}}

−

In my example I want to mount a ntfs-volume, but truecrypt does not use ntfs-3g by default (so there is no write access; checked in version 6.1).

+

In the following example I want to mount a ntfs-volume, but TrueCrypt does not use ''ntfs-3g by'' default (so there is no write access; checked in version 6.1).

The following command works for me:

The following command works for me:

truecrypt --filesystem=ntfs-3g --mount /file/you/want/to/mount

truecrypt --filesystem=ntfs-3g --mount /file/you/want/to/mount

Line 164:

Line 218:

== Mount volumes via fstab ==

== Mount volumes via fstab ==

−

First of all, we need to write a script which will handle the way mounting via fstab is done. Place the following in {{ic|/sbin/mount.truecrypt}}:

−

#!/usr/bin/env sh

+

First of all, we need to write a script which will handle the way mounting via fstab is done. Place the following in {{ic|/usr/bin/mount.truecrypt}}:

to your startup procedure. Do not use the -p switch, this method is more secure. Otherwise everyone can just look up the password via [[ps]] and similar tools, as it is in the process name! [http://thoughtyblog.wordpress.com/2009/07/05/truecrypt-linux-hide-password-from-ps/ source]

+

''password''

+

EOF

+

}}

+

to your startup procedure. Do not use the {{ic|-p}} switch, this method is more secure. Otherwise everyone can just look up the password via ''ps'' and similar tools, as it is in the process name! [http://thoughtyblog.wordpress.com/2009/07/05/truecrypt-linux-hide-password-from-ps/ source]

+

+

The most recent truecrypt has a couple of followup questions. If you have expect installed, this will work (assuming no keyfile and no desire to protect hidden volume), saved to a file with root-only perms called from /etc/rc.local:

+

+

{{bc|<nowiki>

+

#! /bin/bash

+

expect << EOF

+

spawn /usr/bin/truecrypt ''/path/to/EncryptedFile'' ''/mount/point''

+

expect "Enter password"

+

send "volume password\n"

+

expect "Enter keyfile"

+

send "\n"

+

expect "Protect hidden volume"

+

send "\n"

+

expect eof;

+

EOF

+

</nowiki>}}

+

+

Of course, this isn't as secure as entering your password manually. But for some use cases, such as when your TrueCrypt filesystem is in a file on shared storage, it's better than being unencrypted.

+

+

== Safely unmount and unmap volumes (on shutdown) ==

−

==Safely unmount and unmap volumes (on shutdown)==

You can unmount a specific device by

You can unmount a specific device by

−

# truecrypt -d /PATH/TO/MOUNTPOINT

+

# truecrypt -d ''/path/to/mountpoint''

or leave away the path to unmount all truecrypt volumes.

or leave away the path to unmount all truecrypt volumes.

−

If you want your truecrypt device to be unmounted automatically at shutdown, add the following to the file ''/etc/rc.local.shutdown'':

+

If you want your truecrypt device to be unmounted automatically at shutdown, add the following to the file {{ic|/etc/rc.local.shutdown}}:

if (/usr/bin/truecrypt --text --list)

if (/usr/bin/truecrypt --text --list)

Line 285:

Line 354:

}

}

fi

fi

+

You can also leave away the ''sleep'' command, it is just to give the unmounting some time to complete before the actual shutdown.

You can also leave away the ''sleep'' command, it is just to give the unmounting some time to complete before the actual shutdown.

−

If you're using [[systemd]], there is a service trying to unmount truecrypt-encrypted filesystems at shutdown automatically on the [[Systemd/Services]] page.

+

== Errors ==

+

+

=== TrueCrypt is already running ===

−

==Errors==

−

===TrueCrypt is already running===

If a messagebox ''TrueCrypt is already running'' appears when starting TrueCrypt, check for a hidden file in the home directory of the concerned user called ''.TrueCrypt-lock-username''. Substitute ''username'' with the individual username. Delete the file and start TrueCrypt again.

If a messagebox ''TrueCrypt is already running'' appears when starting TrueCrypt, check for a hidden file in the home directory of the concerned user called ''.TrueCrypt-lock-username''. Substitute ''username'' with the individual username. Delete the file and start TrueCrypt again.

−

===Deleted stale lockfile===

+

=== Deleted stale lockfile ===

−

If you always get a message "Delete stale lockfile [....]" after starting Truecrypt, the Truecrypt process with the lowest ID has to be killed during Gnome log out. A user in the Ubuntuforum provided the following solution: edit

+

−

/etc/gdm/PostSession/Default

+

If you always get a message "Delete stale lockfile [....]" after starting Truecrypt, the Truecrypt process with the lowest ID has to be killed during Gnome log out. Edit {{ic|/etc/gdm/PostSession/Default}} and add the following line before exit 0:

−

and add the following line before exit 0:

+

kill $(ps -ef | grep truecrypt | tr -s ' ' | cut -d ' ' -f 2)

−

kill `ps -ef | grep truecrypt | tr -s ' ' | cut -d ' ' -f 2`

+

+

=== Issues with Unicode file/folder names ===

+

+

==== NTFS ====

−

===Issues with Unicode file / folder names ===

−

====NTFS====

Should files resp. folders containing Unicode characters in their names be incorrectly or not at all displayed on TrueCrypt NTFS volumes (while e. g. being correctly handled on non-encrypted NTFS partitions), first verify that you have the [[NTFS-3G]] driver installed and then create the following symlink as root:

Should files resp. folders containing Unicode characters in their names be incorrectly or not at all displayed on TrueCrypt NTFS volumes (while e. g. being correctly handled on non-encrypted NTFS partitions), first verify that you have the [[NTFS-3G]] driver installed and then create the following symlink as root:

Similarly, FAT32 volumes created using Windows may use Unicode rather than ISO 8859-1. In order to use UTF-8 globally, set the mount option:

−

Similarly, FAT32 volumes created using Windows may use Unicode rather than ISO 8859-1. In order to use UTF-8, set the mount option

iocharset=utf8

iocharset=utf8

−

when mounting such volumes, or globally as described above.

−

===Unmount error (device mapper)===

+

Alternatively, when mounting volumes locally use:

+

--fs-options=iocharset=utf8

+

+

Since [https://bugs.archlinux.org/task/56781 linux-4.14.4], UTF8 charset is enabled by default. So in order to mount volumes using ISO 8859-1 encoding, you need to set the following option:

+

--fs-options=utf8=no

+

+

=== Unmount error (device mapper) ===

+

If you always get a message "device-mapper: remove ioctl failed: Device or resource busy" when attempting to dismount your truecrypt volume, the solution is to goto: Setting > Preferences > System Integration > Kernel Service and check the box

If you always get a message "device-mapper: remove ioctl failed: Device or resource busy" when attempting to dismount your truecrypt volume, the solution is to goto: Setting > Preferences > System Integration > Kernel Service and check the box

Do not use kernel cryptographic services

Do not use kernel cryptographic services

−

{{Note|I have only seen this with a truecrypt partition. Not with a truecrypt file.}}

−

===Failed to set up a loop device===

+

=== Mount error (device mapper, truecrypt partition) ===

+

+

When attempting to mount your truecrypt volume, a message like this one may appear:

+

+

Error: device-mapper: create ioctl failed: Device or resource busy

+

Command failed

+

If so, run:

+

# cryptsetup remove /dev/mapper/truecrypt1

+

+

=== Failed to set up a loop device ===

+

If you get a message "Failed to set up a loop device" when trying to create/mount a TrueCrypt volume, it may be because you updated your kernel recently without rebooting.

If you get a message "Failed to set up a loop device" when trying to create/mount a TrueCrypt volume, it may be because you updated your kernel recently without rebooting.

Rebooting should fix this error.

Rebooting should fix this error.

−

Otherwise, check if {{ic|loop}} has been loaded as kernel module:

+

Otherwise, check if ''loop'' has been loaded as kernel module:

−

lsmod | grep loop

+

$ lsmod | grep loop

−

If not listed, retry the TrueCrypt command after {{ic|modprobe loop}}. Should it work, consider to add {{ic|loop}} to the MODULES array in {{ic|/etc/modules-load.d}}:

+

If not listed, retry the TrueCrypt command after {{ic|modprobe loop}}. Should it work, consider to add ''loop'' to the modules in {{ic|/etc/modules-load.d}}:

# tee /etc/modules-load.d/truecrypt.conf <<< "loop"

# tee /etc/modules-load.d/truecrypt.conf <<< "loop"

Line 335:

Line 422:

{{Note|As of udev 181-5, the loop device module is no longer auto-loaded, and the procedure described here is necessary.}}

{{Note|As of udev 181-5, the loop device module is no longer auto-loaded, and the procedure described here is necessary.}}

−

==Related links==

+

With newer kernel versions there are no loop devices created at startup. If there are no loop devices the first time mounting a container file, TrueCrypt fails ("Failed to set up a loop device") but also creates the maximum number of loop devices (usually 256), mounting should now work.

* [http://www.privacylover.com/encryption/analysis-is-there-a-backdoor-in-truecrypt-is-truecrypt-a-cia-honeypot/ There is a good chance the CIA has a backdoor?] (via [https://secure.wikimedia.org/wikipedia/en/wiki/Truecrypt wp])

* [http://www.privacylover.com/encryption/analysis-is-there-a-backdoor-in-truecrypt-is-truecrypt-a-cia-honeypot/ There is a good chance the CIA has a backdoor?] (via [https://secure.wikimedia.org/wikipedia/en/wiki/Truecrypt wp])

Consider using VeraCrypt, a TrueCrypt fork in active development installable with the veracrypt package; VeraCrypt storage format is compatible with TrueCrypt storage format since version 1.0f.

Warning: On 2015/09/26 two critical security issues has been found in Windows version of TrueCrypt: CVE-2015-7358 and CVE-2015-7359. Take this into account if you're planning to use this software to share encrypted volumes between Windows and ArchLinux. More information: 12

Installation

Note: For opening and accessing an existing TrueCrypt container cryptsetup is the preferred way, since it is well integrated with the rest of the system. Creating a new TrueCrypt container can be done using truecrypt, after which it can be opened using cryptsetup.

If you are using truecrypt to encrypt a virtual filesystem (e.g. a file), the module will be automatically loaded whenever you run the truecrypt command.

If you are using truecrypt to encrypt a physical device (e.g. a hard disk or usb drive), you will likely want to load the module during the boot sequence:

Add the module to /etc/modules-load.d/:

# tee /etc/modules-load.d/truecrypt.conf <<< "truecrypt"

Note:

This didn't work for me (module truecrypt seems to be non-existent now), but adding "loop" module worked

# tee /etc/modules-load.d/truecrypt.conf <<< "loop"
# modprobe loop

It does not appear that loading a module applies with TrueCrypt 7.1a, the current version in Arch as of 4/19/2013. The above advice may be outdated with respect to the module, however it is still important to enable FUSE, loop and your encryption algorithm (e.g. AES, XTS, SHA512) in custom kernels.

If you only want to open and access an existing truecrypt container, this can also be done with cryptsetup i.e. without installing Truecrypt.

Accessing a TrueCrypt or VeraCrypt container using cryptsetup

Since version 1.6.7, cryptsetup supports opening TrueCrypt and VeraCrypt containers natively, without the need of the truecrypt or veracrypt package. Use the following command as a guideline.

$ cryptsetup --type tcrypt open container-to-mount container-name

To mount a VeraCrypt cointainer, you must use the --veracrypt option alongside --type tcrypt. If using a custom Personal Iteration Multiplier (PIM), use the --veracrypt-query-pim option to be promoted for the PIM.

Replace container-to-mount with the device file under /dev or the path to the file you wish to open. Upon successful opening, the plaintext device will appear as /dev/mapper/container-name, which you can mount like any normal device.

If you are using key files, supply them using the --key-file option, to open a hidden volume, supply the --tcrypt-hidden option and for a partition or whole drive that is encrypted in system mode use the --tcrypt-system option.

Automounting using /etc/crypttab

Since version 206, systemd supports (auto)mounting TrueCrypt containers at boot or runtime using /etc/crypttab.

The following example setup will mount /dev/sda2 in system encryption mode as soon as /mnt/truecrypt-volume is accessed using systemd's automounting logic. The passphrase to open the volume is given in /etc/volume.password. Note that the device file given in /etc/fstab needs to be the one from /dev/mapper/ and not, for example, from /dev/disk/by-uuid/ for automounting logic to kick in. Other than that you can still reliably identify the encrypted volume itself inside of /etc/crypttab using device file names from /dev/disk/.

/etc/crypttab

truecrypt-volume /dev/sda2 /etc/volume.password tcrypt-system,noauto

For a standard truecrypt volume, use tcrypt instead of tcrypt-system. And for a hidden one, use tcrypt-hidden.

Encrypting a file as a virtual volume

The following instructions will create a file that will act as a virtual filesystem, allowing you to mount it and store files within the encrypted file. This is a convenient way to store sensitive information, such as financial data or passwords, in a single file that can be accessed from Linux, Windows, or Macs.

To create a new truecrypt file interactively, type the following in a terminal:

$ truecrypt -t -c

Follow the instructions, choosing the default values unless you know what you are doing:

Note: Truecrypt requires root privileges and as such, running the above command as a user will attempt to use sudo for authentication. To work with files as a regular user, please seeMount volumes as a normal user.

Once mounted, you can copy or create new files within the encrypted directory as if it was any normal directory. When you are you ready to re-encrypt the contents and unmount the directory, run:

$ truecrypt -t -d

Again, this will require administrator privileges through the use of sudo. After running it check if the files that are to be encrypted are indeed no longer in the directory. (might want to try unimportant data first) If they are still there, note that rm doesn't make the data unrecoverable.

For more information about truecrypt in general, run:

$ man truecrypt

Note: As of 1:7.1a-1 dont see a man or info page.

Several options can be passed at the command line, making automated access and creation a simple task. The man page is highly recommended reading.

Encrypting a physical volume

Note: If you are having problems with the graphical interface, you can run in CLI mode with the -t flag.

If you want to use a keyfile, create one with this command:

truecrypt --create-keyfile /etc/disk.key

By default both passphrase and key will be needed to unlock the volume.

Create a new volume in the device /dev/sda1:

# truecrypt --volume-type=normal -c /dev/sda1

Map the volume to /dev/mapper/truecrypt1:

# truecrypt -N 1 /dev/sda1

If this command does not for you try this to map the volume:

# truecrypt --filesystem=none --slot=1 /dev/sda1

Simply format the disk like you normally would choosing your favourite file system, except use the path /dev/mapper/truecrypt1. E.g. for ext4 use:

Automatic mount on login

to your startup procedure. Do not use the -p switch, this method is more secure. Otherwise everyone can just look up the password via ps and similar tools, as it is in the process name! source

The most recent truecrypt has a couple of followup questions. If you have expect installed, this will work (assuming no keyfile and no desire to protect hidden volume), saved to a file with root-only perms called from /etc/rc.local:

You can also leave away the sleep command, it is just to give the unmounting some time to complete before the actual shutdown.

Errors

TrueCrypt is already running

If a messagebox TrueCrypt is already running appears when starting TrueCrypt, check for a hidden file in the home directory of the concerned user called .TrueCrypt-lock-username. Substitute username with the individual username. Delete the file and start TrueCrypt again.

Deleted stale lockfile

If you always get a message "Delete stale lockfile [....]" after starting Truecrypt, the Truecrypt process with the lowest ID has to be killed during Gnome log out. Edit /etc/gdm/PostSession/Default and add the following line before exit 0:

kill $(ps -ef | grep truecrypt | tr -s ' ' | cut -d ' ' -f 2)

Issues with Unicode file/folder names

NTFS

Should files resp. folders containing Unicode characters in their names be incorrectly or not at all displayed on TrueCrypt NTFS volumes (while e. g. being correctly handled on non-encrypted NTFS partitions), first verify that you have the NTFS-3G driver installed and then create the following symlink as root:

ln -s /sbin/mount.ntfs-3g /sbin/mount.ntfs

That will cause TrueCrypt to automatically use this driver for NTFS volumes, having the same effect as the explicit use of

FAT

Similarly, FAT32 volumes created using Windows may use Unicode rather than ISO 8859-1. In order to use UTF-8 globally, set the mount option:

iocharset=utf8

Alternatively, when mounting volumes locally use:

--fs-options=iocharset=utf8

Since linux-4.14.4, UTF8 charset is enabled by default. So in order to mount volumes using ISO 8859-1 encoding, you need to set the following option:

--fs-options=utf8=no

Unmount error (device mapper)

If you always get a message "device-mapper: remove ioctl failed: Device or resource busy" when attempting to dismount your truecrypt volume, the solution is to goto: Setting > Preferences > System Integration > Kernel Service and check the box

Do not use kernel cryptographic services

Mount error (device mapper, truecrypt partition)

When attempting to mount your truecrypt volume, a message like this one may appear:

Failed to set up a loop device

If you get a message "Failed to set up a loop device" when trying to create/mount a TrueCrypt volume, it may be because you updated your kernel recently without rebooting.
Rebooting should fix this error.

Otherwise, check if loop has been loaded as kernel module:

$ lsmod | grep loop

If not listed, retry the TrueCrypt command after modprobe loop. Should it work, consider to add loop to the modules in /etc/modules-load.d:

# tee /etc/modules-load.d/truecrypt.conf <<< "loop"

Note: As of udev 181-5, the loop device module is no longer auto-loaded, and the procedure described here is necessary.

With newer kernel versions there are no loop devices created at startup. If there are no loop devices the first time mounting a container file, TrueCrypt fails ("Failed to set up a loop device") but also creates the maximum number of loop devices (usually 256), mounting should now work.

To avoid this you can create a loop device before mounting a file:

# mknod -m 0660 /dev/loop8 b 7 8

This creates /dev/loop8. Or create some loop devices at startup:

# echo "options loop max_loop=8" > /etc/modprobe.d/eightloop.conf

Change max_loop=8 to the number of devices you need.

System partition passwords need en_US keymap

If you are using Xorg (which you most likely are, should you not know what that is), use the following command to use US keymap until restart:

# setxkbmap us

Permission denied on NTFS volume

If you cannot modify the filesystem, although permissions seem to be correct, this can be a result of not having NTFS-3G installed, see NTFS.