See crypttab(5) for more details and options supported. It is useful with NTFS for mounting as a normal user. Instead of auto, you can put directly your filesystem, and put usual mount options. etc/fstab /dev/mapper/truecrypt-volume /mnt/truecrypt-volume auto noauto,tomount 0 0 For a veracrypt volume, use tcrypt-veracrypt alongside tcrypt. etc/crypttab truecrypt-volume /dev/sda2 /etc/volume.password tcrypt-system,noautoįor a standard truecrypt volume, use tcrypt instead of tcrypt-system. Other than that you can still reliably identify the encrypted volume itself inside of /etc/crypttab using device file names from /dev/disk/. 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. The passphrase to open the volume is given in /etc/volume.password. 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. Since version 206, systemd supports (auto)mounting TrueCrypt containers at boot or runtime using /etc/crypttab. See cryptsetup(8) for more details and all supported options. 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.
Upon successful opening, the plaintext device will appear as /dev/mapper/container-name, which you can mount like any normal device. Replace container-to-mount with the device file under /dev or the path to the file you wish to open.
If using a custom Personal Iteration Multiplier (PIM), use the -veracrypt-query-pim option to be promoted for the PIM. To mount a VeraCrypt cointainer, you must use the -veracrypt option alongside -type tcrypt. $ cryptsetup -type tcrypt open container-to-mount container-name
Use the following command as a guideline. Since version 1.6.7, cryptsetup supports opening TrueCrypt and VeraCrypt containers natively, without the need of the truecrypt or veracrypt package. without installing Truecrypt.Īccessing a TrueCrypt or VeraCrypt container using cryptsetup If you only want to open and access an existing truecrypt container, this can also be done with cryptsetup i.e. 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.
0 kommentar(er)
