This is the recommended solution if you want to use one common partition for all user's home partitions or automatically mount another encrypted block device. Using the /etc/crypttab configuration file, unlocking happens at boot time by systemd's automatic parsing. There are three different solutions for automating the process of unlocking the partition and mounting its filesystem. For other desktops, zulucrypt AUR also provides a GUI. Thunar) to mount the partition, and a password dialog will pop-up. One can use a file manager with gvfs support (e.g. Tip: GVFS can also mount encrypted partitions. Mount the file system to /home, or if it should be accessible to only one user to /home/ username, see #Manual mounting and unmounting. Now create a file system of your choice with: To gain access to the encrypted partition, unlock it with the device mapper, using:Īfter unlocking the partition, it will be available at /dev/mapper/ name. See Dm-crypt/Device encryption#Encryption options for LUKS mode for details like the available options. Replace device with the previously created partition. Then prepare the partition by securely erasing it, see Dm-crypt/Drive preparation#Secure erasure of the hard disk drive.Ĭreate the partition which will contain the encrypted container. Delete the partition and create an empty one if it has a file system. Tip: You can either have a single user's /home directory on a partition, or create a common partition for all user's /home directories.įirst make sure the partition is empty (has no file system attached to it).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |