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

'''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.

Line 6:

Line 13:

* All encryption algorithms use the LRW mode of operation, which is more secure than CBC mode with predictable initialization vectors for storage encryption.

* All encryption algorithms use the LRW mode of operation, which is more secure than CBC mode with predictable initialization vectors for storage encryption.

* "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]].

== Installation ==

== Installation ==

−

Type as root in a terminal:

−

# pacman -S truecrypt

−

If you use any kernel other than {{Package Official|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 <code>truecrypt</code> command. You will need the "loop" module though. Add it to the MODULES array in /etc/rc.conf.

+

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

+

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 '''truecrypt''' command. Add it to the MODULES array in /etc/rc.conf.

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/rc.conf:

+

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

−

MODULES=('''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 <code>fuse</code> and your encryption algorithm (e.g. <code>AES</code>, <code>XTS</code>, <code>SHA512</code>) in custom kernels.}}

+

{{Note|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.}}

== 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 won't 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're doing:

+

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 ''{{Codeline|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 {{Codeline|sudo}}.

+

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

$ 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 ==

+

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 /dev/sda1:

−

truecrypt --type normal -c /dev/sda1

+

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

Map the volume to /dev/mapper/truecrypt1:

Map the volume to /dev/mapper/truecrypt1:

−

truecrypt -N 1 /dev/sda1

+

truecrypt -N 1 /dev/sda1

−

If this command doesn't 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.

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.

−

mkfs.ext3 /dev/mapper/truecrypt1

+

mkfs.ext3 /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.

First, create a normal outer volume as described above.

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

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

−

truecrypt -N 1 /dev/sda1

+

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:

Line 132:

Line 142:

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.ext3 /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 ==

+

+

{{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.}}

−

==Mount a special filesystem==

+

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 my example I want to mount a ntfs-volume, but truecrypt doesn't use ntfs-3g by default (so there is no write access; checked in version 6.1).

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]

+

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]

+

+

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:

+

+

#! /bin/bash

+

expect << EOF

+

spawn /usr/bin/truecrypt /path/to/myEncryptedFile /mnt/point

+

expect "Enter password"

+

send "somelonggoodpassword\n"

+

expect "Enter keyfile"

+

send "\n"

+

expect "Protect hidden volume"

+

send "\n"

+

expect eof;

+

EOF

+

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

Line 223:

Line 297:

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)

+

then {

/usr/bin/truecrypt -d

/usr/bin/truecrypt -d

sleep 3

sleep 3

+

}

+

fi

+

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.

−

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

+

== 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

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

/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 on NTFS volumes ===

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, set the mount option

+

iocharset=utf8

+

when mounting such volumes, or globally as described above.

+

+

=== 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.}}

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

−

==Related links==

+

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

−

* [http://www.truecrypt.org/ TrueCrypt Homepage]

+

+

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.

+

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 {{ic|modprobe loop}}. Should it work, consider to add {{ic|loop}} to the modules in {{ic|/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.}}

* [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])

Installation

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. Add it to the MODULES array in /etc/rc.conf.

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: 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.

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:

Volume type:
1) Normal
2) Hidden
Select [1]: 1

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

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

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

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.

mkfs.ext3 /dev/mapper/truecrypt1

Mount the volume:

mount /dev/mapper/truecrypt1 /media/disk

Map and mount a volume:

truecrypt /dev/sda1 /media/disk

Unmount and unmap a volume:

truecrypt -d /dev/sda1

Creating a hidden volume

First, create a normal outer volume as described above.

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

truecrypt -N 1 /dev/sda1

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

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.

Unmap the outer truecrypt volume and map the hidden one:

truecrypt -d /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.

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.

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

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. A user in the Ubuntuforum provided the following solution: 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, set the mount option

iocharset=utf8

when mounting such volumes, or globally as described above.

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

Note: I have only seen this with a truecrypt partition. Not with a truecrypt file.

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.