Difference between revisions of "Pam mount"

From ArchWiki
Jump to: navigation, search
m (GDM)
(GDM: rw)
 
(21 intermediate revisions by 14 users not shown)
Line 1: Line 1:
 +
{{DISPLAYTITLE:pam_mount}}
 
[[Category:Security]]
 
[[Category:Security]]
To have an encrypted home partition (encrypted with, for example, LUKS or ecryptfs) mounted automatically when logging in, you can use pam_mount. It will mount your /home (or whatever mount point you like) when you log in using your login manager or when logging in on console. The encrypted drive's passphrase should be the same as your linux user's password, so you do not have to type in two different passphrases to login.
+
[[ja:Pam mount]]
 +
{{Style|See [[Help:Style]] and related.}}
 +
 
 +
{{Related articles start}}
 +
{{Related|dm-crypt/Mounting at login}}
 +
{{Related|PAM}}
 +
{{Related articles end}}
 +
[http://pam-mount.sourceforge.net/ pam_mount] can be used to automatically mount an encrypted home partition (encrypted with, for example, [[LUKS]] or [[ECryptfs]]) on user log in.  
 +
It will mount your /home (or whatever mount point you like) when you log in using your login manager or when logging in on console. The encrypted drive's passphrase should be the same as your linux user's password, so you do not have to type in two different passphrases to login.
 +
 
 +
{{Warning|Pam_mount can also unmount your partitions when you close your last session but this is currently not working due to the use of pam_systemd.so in the pam stack.}}
  
 
==General Setup==
 
==General Setup==
  
#Install {{pkg|pam_mount}} from the [[Official Repositories]].
+
#Install {{pkg|pam_mount}} from the [[Official repositories]].
 
#Edit /etc/security/pam_mount.conf.xml as follows:
 
#Edit /etc/security/pam_mount.conf.xml as follows:
  
Line 11: Line 22:
 
*USERNAME should be replaced with your linux-username.
 
*USERNAME should be replaced with your linux-username.
 
*/dev/sdaX should be replaced with the corresponding device or container file.
 
*/dev/sdaX should be replaced with the corresponding device or container file.
*fstype="auto" can be changed to any <type> that is present in /sbin/mount.<type>. "auto" should work fine in most cases.
+
*fstype="auto" can be changed to any <type> that is present in /usr/bin/mount.<type>. "auto" should work fine in most cases.  Use fstype="crypt" so that the loop device gets closed at logout for volumes needing it.
 
*Add mount options, if needed.
 
*Add mount options, if needed.
  
Line 23: Line 34:
 
==Login Manager Configuration==
 
==Login Manager Configuration==
  
In general, you have to edit configuration files in /etc/pam.d so that pam_mount will be called on login. The correct order of entries in each file is important. It is probably necessary to change both /etc/pam.d/login and the file for your display manager (e.g., Slim or GDM). Example configuration files follow, with the added lines in bold.
+
In general, you have to edit configuration files in /etc/pam.d so that pam_mount will be called on login. The correct order of entries in each file is important. It is necessary to edit /etc/pam.d/system-auth as shown below. If you use a display manager (e.g., Slim or GDM) edit its file, too. Example configuration files follow, with the added lines in bold.
  
 
{{hc|/etc/pam.d/system-auth|2=
 
{{hc|/etc/pam.d/system-auth|2=
Line 48: Line 59:
 
}}
 
}}
  
You may need to add similar lines to /etc/pam.d/su and /etc/pam.d/sudo, depending on how you use su and sudo, respectively.
+
=== SLiM ===
  
=== [[Slim]] ===
+
For [[SLiM]]:
  
 
{{hc|/etc/pam.d/slim|
 
{{hc|/etc/pam.d/slim|
Line 67: Line 78:
 
}}
 
}}
  
=== [[GDM]] ===
+
=== GDM ===
  
Note that the configuration file has changed to be /etc/pam.d/gdm-password (instead of /etc/pam.d/gdm) as of GDM version 3.2.
+
Manual configuration for GDM is not needed, since it relies on {{ic|/etc/pam.d/system-auth}}.
 
+
{{hc|/etc/pam.d/gdm.password|2=
+
#%PAM-1.0
+
auth           requisite      pam_nologin.so
+
auth            required        pam_env.so
+
 
+
auth            requisite      pam_unix.so nullok
+
'''auth         optional        pam_mount.so'''
+
auth            optional        pam_gnome_keyring.so
+
 
+
auth            sufficient      pam_succeed_if.so uid >= 1000 quiet
+
auth            required        pam_deny.so
+
 
+
account        required        pam_unix.so
+
 
+
password        required        pam_unix.so
+
'''password        optional        pam_mount.so'''
+
 
+
session        required        pam_loginuid.so
+
-session        optional        pam_systemd.so
+
session        optional        pam_keyinit.so force revoke
+
session        required        pam_limits.so
+
session        required        pam_unix.so
+
'''session        optional        pam_mount.so'''
+
session        optional        pam_gnome_keyring.so auto_start
+
}}
+

Latest revision as of 22:19, 20 July 2016

Tango-edit-clear.pngThis article or section needs language, wiki syntax or style improvements.Tango-edit-clear.png

Reason: See Help:Style and related. (Discuss in Talk:Pam mount#)

pam_mount can be used to automatically mount an encrypted home partition (encrypted with, for example, LUKS or ECryptfs) on user log in. It will mount your /home (or whatever mount point you like) when you log in using your login manager or when logging in on console. The encrypted drive's passphrase should be the same as your linux user's password, so you do not have to type in two different passphrases to login.

Warning: Pam_mount can also unmount your partitions when you close your last session but this is currently not working due to the use of pam_systemd.so in the pam stack.

General Setup

  1. Install pam_mount from the Official repositories.
  2. Edit /etc/security/pam_mount.conf.xml as follows:

Insert 2 new lines at the end of the file, but before the last closing tag, </pam_mount>. Notes:

  • USERNAME should be replaced with your linux-username.
  • /dev/sdaX should be replaced with the corresponding device or container file.
  • fstype="auto" can be changed to any <type> that is present in /usr/bin/mount.<type>. "auto" should work fine in most cases. Use fstype="crypt" so that the loop device gets closed at logout for volumes needing it.
  • Add mount options, if needed.
/etc/security/pam_mount.conf.xml
<volume user="USERNAME" fstype="auto" path="/dev/sdaX" mountpoint="/home" options="fsck,noatime" />
<mkmountpoint enable="1" remove="true" />

</pam_mount>

Login Manager Configuration

In general, you have to edit configuration files in /etc/pam.d so that pam_mount will be called on login. The correct order of entries in each file is important. It is necessary to edit /etc/pam.d/system-auth as shown below. If you use a display manager (e.g., Slim or GDM) edit its file, too. Example configuration files follow, with the added lines in bold.

/etc/pam.d/system-auth
#%PAM-1.0

auth      required  pam_env.so
auth      required  pam_unix.so     try_first_pass nullok
auth      optional  pam_mount.so
auth      optional  pam_permit.so

account   required  pam_unix.so
account   optional  pam_permit.so
account   required  pam_time.so

password  optional  pam_mount.so
password  required  pam_unix.so     try_first_pass nullok sha512 shadow
password  optional  pam_permit.so

session   optional  pam_mount.so
session   required  pam_limits.so
session   required  pam_env.so
session   required  pam_unix.so
session   optional  pam_permit.so

SLiM

For SLiM:

/etc/pam.d/slim
auth            requisite       pam_nologin.so
auth            required        pam_env.so
auth            required        pam_unix.so
auth            optional        pam_mount.so
account         required        pam_unix.so
password        required        pam_unix.so
password        optional        pam_mount.so
session         required        pam_limits.so
session         required        pam_unix.so
session         optional        pam_mount.so
session         optional        pam_loginuid.so
session         optional        pam_ck_connector.so

GDM

Manual configuration for GDM is not needed, since it relies on /etc/pam.d/system-auth.