Difference between revisions of "Dm-crypt/Mounting at login"

From ArchWiki
Jump to navigation Jump to search
(change category to Category:Disk encryption)
m (spanish interlanguage link)
Line 1: Line 1:
[[Category:Disk encryption]]
[[Category:Disk encryption]]
[[es:Dm-crypt/Mounting at login]]
{{Related articles start}}
{{Related articles start}}

Revision as of 17:33, 26 September 2018

It is possible to configure PAM and systemd to automatically mount a dm-crypt encrypted home partition when its owner logs in, and to unmount it when he logs out.

This tutorial assumes you have already created your encrypted partition, as described in Dm-crypt/Encrypting a non-root file system.

  • You need to use the same password for your user account and for LUKS.
  • In all the examples, replace YOURNAME with your username, 1000 with your user ID and PARTITION with the name of your encrypted partition's device.

Mounting at login

pam_exec can be used to unlock the device at login. Edit /etc/pam.d/system-login and add the line below emphasized in bold after auth include system-auth:

Note: GDM, LightDM, and maybe other display managers might require pam_exec for session as well, see Talk:Dm-crypt/Mounting at login#pam_exec required for session & using script.

Tango-view-refresh-red.pngThis article or section is out of date.Tango-view-refresh-red.png


auth       include    system-auth
auth       optional   pam_exec.so expose_authtok quiet /usr/bin/cryptsetup open /dev/PARTITION home-YOURNAME


Now edit /etc/fstab to mount the unlocked device using systemd.automount:


/dev/mapper/home-YOURNAME  /home/YOURNAME     ext4            rw,noatime,noauto,x-systemd.automount 0 2


Your home directory will be mounted automatically on the first access made by your desktop environment or shell.

Unmouting at logout

After you log out of all your sessions, systemd-logind automatically shuts down user@1000.service. Therefore, you can specify that your mountpoint requires it, and systemd will unmount it automatically:


This will however create a circular dependency loop that cannot by resolved automatically by systemd, so you need to describe the dependencies and ordering explicitly:

Note: If your desktop environment or some other application does not kill all its processes on logout, you might need to set KillUserProcesses=yes in /etc/systemd/logind.conf.


After unmounting, the device will still be unlocked, and it will be possible to mount it without re-entering password. You can set up and enable a service that starts when the device gets unlocked (BindsTo=dev-mapper-home\x2dYOURNAME.device) and dies after the device gets unmounted (Requires,Before=home-YOURNAME.mount), locking the device in the process (ExecStop=cryptsetup close):


ExecStop=/usr/bin/cryptsetup close home-YOURNAME

Note: dev-PARTITION is the result of systemd-escape -p /dev/PARTITION