| 2019-05-24 07:09:17 |
Christian Ehrhardt |
description |
The pam_mount module does not mount the volumes that contain defined control attributes (user, pgrp, sgrp, uid, and gid).
I believe that it simply ignores all volume tags that contain this control, because even with debug enable ="1" nothing is registered in syslog. Only volumes that are defined without any type of control attribute work and produce information in the log.
It has been tested in the following environment:
Ubuntu 18.04.2 LTS
libpam-mount 2.16-3ubuntu0.1 |
The pam_mount module does not mount the volumes that contain defined control attributes (user, pgrp, sgrp, uid, and gid).
I believe that it simply ignores all volume tags that contain this control, because even with debug enable ="1" nothing is registered in syslog. Only volumes that are defined without any type of control attribute work and produce information in the log.
Example:
It works:
<volume fstype="cifs" server="FILESERVER" path="SHARE$" mountpoint="~/SHARE" options="gid=MYGROUP,file_mode=0770,dir_mode=0770" />
It does not work:
<volume sgrp="MYGROUP" fstype="cifs" server="FILESERVER" path="SHARE$" mountpoint="~/SHARE" options="gid=MYGROUP,file_mode=0770,dir_mode=0770" />
It has been tested in the following environments:
* Ubuntu 18.04.2 LTS
* libpam-mount 2.16-3ubuntu0.1
* Ubuntu 19.04
* libpam-mount:amd64 2.16-9ubuntu2 |
|
