pam_mount doesn't mount when using sgrp

Bug #1580237 reported by CMAH on 2016-05-10
24
This bug affects 5 people
Affects Status Importance Assigned to Milestone
samba (Ubuntu)
Undecided
Unassigned

Bug Description

Prior to version 2:4.3.8+dfsg this worked:
<volume icase="no" sgrp="SOME_NON_PRIMATY_GROUP" fstype="cifs" server="10.10.10.1" path="my/Shared Folder/Here" mountpoint="/home/%(USER)/SOME_NON_PRIMATY_GROUP" options="uid=%(USER),gid=SOME_NON_PRIMATY_GROUP,iocharset=utf8,file_mode=0770,dir_mode=0770,workgroup=my.domain" />
Now it doesn't mount and doesn´t even show an attempt or errors in auth.log.
Mount by primary group (gid) still works.

Marc Deslauriers (mdeslaur) wrote :

Hi, thanks for reporting this.

Have you tried 4.3.9 that got released as an update?

CMAH (informacica) wrote :

Hello.
I should have said this earlier (this is my first bug report), I am know on version 4.3.9 and the mount still doesn't happen.
Also, this works fine:
<volume icase="no" gid="MyPrimaryGroupGID" fstype="cifs" server="10.10.10.1" path="my/Shared Folder/Here" mountpoint="/home/%(USER)/SOME_NON_PRIMATY_GROUP" options="uid=%(USER),gid=SOME_NON_PRIMATY_GROUP,iocharset=utf8,file_mode=0770,dir_mode=0770,workgroup=my.domain" />
This led me to believe the problem is in sgrp.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in samba (Ubuntu):
status: New → Confirmed

I confirm the bug, because since version "2:4.3.8+dfsg-0ubuntu0.14.04.2" current "2:4.3.9+dfsg-0ubuntu1" that cifs volumes with the attribute "sgrp" in pam_mount are unmounted.

Hi,

Just try to see if this fixes:
* Upgrade to the latest version (on 14.04, 4.3.9);
* Add to /etc/samba/smb.conf file in the [global] section on the client:
    winbind expand groups = 1
* Restart smbd, nmbd and winbind

Fixed your same issue. sgrp seems to mount right after this procedure.

@CMAH:
Per the former comment, does that mean this was just a change to the way Samba handles its configuration and is "winbind expand groups = 1" a valid fix on the config side?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers