libpam-mount doesn't pass options to mount.fuse correctly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libpam-mount (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: libpam-mount
libpam-mount combines the -o options flag and the options specified in /etc/security/
Oct 18 10:47:04 valiant sshd[15676]: pam_mount(
Oct 18 10:47:04 valiant sshd[15676]: command: 'mount.fuse' 'encfs#
Oct 18 10:47:04 valiant sshd[15678]: pam_mount(
Oct 18 10:47:04 valiant sshd[15678]: pam_mount(
Oct 18 10:47:04 valiant sshd[15676]: pam_mount(
Oct 18 10:47:04 valiant sshd[15676]: pam_mount(
Oct 18 10:47:04 valiant sshd[15676]: pam_mount(
Oct 18 10:47:04 valiant sshd[15676]: pam_mount(
Oct 18 10:47:04 valiant sshd[15676]: pam_mount(
The attached patch separates the -o and the options into two command-line arguments:
Oct 18 10:52:57 valiant gdm-session-
Oct 18 10:52:57 valiant gdm-session-
Oct 18 10:52:57 valiant gdm-session-
Oct 18 10:52:57 valiant gdm-session-
egid=100)
Oct 18 10:52:57 valiant gdm-session-
Oct 18 10:52:57 valiant gdm-session-
(note that the 'error' referred to in the second log file excerpt is not an error, and the mount does in fact succeed in this case)
This could, of course, equally well have been fixed by making mount.fuse's command-line parsing more robust.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: libpam-mount 2.3-1 [modified: lib/security/
ProcVersionSign
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Mon Oct 18 11:00:19 2010
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: libpam-mount
tags: | added: patch |
Changed in libpam-mount (Ubuntu): | |
status: | New → Confirmed |
Changed in libpam-mount (Ubuntu): | |
status: | Confirmed → Fix Released |
This should not be needed, as fuse, since version 2.4.0, uses getopt_long and thus should be able to understand squashed options.