Your message dated Thu, 24 Feb 2005 12:17:37 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#296417: fixed in libpam-mount 0.9.22-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 22 Feb 2005 11:30:46 +0000
>From [EMAIL PROTECTED] Tue Feb 22 03:30:46 2005
Return-path: <[EMAIL PROTECTED]>
Received: from srv3.handshake.de [193.141.176.9]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1D3YFZ-0006pa-00; Tue, 22 Feb 2005 03:30:45 -0800
Received: from webmail3.handshake.de (localhost [127.0.0.1])
by srv3.handshake.de (Postfix) with SMTP
id E78C731FBF; Tue, 22 Feb 2005 12:48:18 +0100 (CET)
Received: from 84.128.195.113
(SquirrelMail authenticated user undoman)
by webmail3.handshake.de with HTTP;
Tue, 22 Feb 2005 12:48:18 +0100 (CET)
Message-ID: <[EMAIL PROTECTED]>
Date: Tue, 22 Feb 2005 12:48:18 +0100 (CET)
Subject: libpam-mount: does not mount smb shares with whitespace
From: "Marcus Schommer" <[EMAIL PROTECTED]>
To: "Debian Bug Tracking System" <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
User-Agent: SquirrelMail/1.4.2
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
X-Priority: 3
Importance: Normal
Content-Transfer-Encoding: quoted-printable
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.8 required=4.0 tests=BAYES_00,HAS_PACKAGE,
PRIORITY_NO_NAME autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: libpam-mount
Version: 0.9.20-11
Severity: important
hi,
i have smb shares with whitespaces which libpam-mount refuses to mount.
user _schommer_ is configured to be handled by libpam-mount. the user
configuration file shows:
so01:~# cat /home/schommer/.pam_mount.conf
volume schommer smb ntserver "test frgb" /home/schommer/mnt/test - - -
-- snip --
i've tried different combinations of " and \ for escaping the
whitespace but it had no positive effects.
i think the essential message from the debug output is:
Could not resolve mount point frgb
with _frgb_ beeing the second part of the share after the whitespace.
heres the complete debug output:
Feb 22 12:02:32 so01 login[3530]: pam_mount: path to luserconf set to
/home/schommer/.pam_mount.conf
Feb 22 12:02:32 so01 login[3530]: pam_mount: reading options_allow...
Feb 22 12:02:32 so01 login[3530]: pam_mount: back from global readconfig
Feb 22 12:02:32 so01 login[3530]: pam_mount: going to readconfig user
Feb 22 12:02:32 so01 login[3530]: pam_mount: back from user readconfig
Feb 22 12:02:32 so01 login[3530]: pam_mount: real and effective user ID
are 0 and 0.
Feb 22 12:02:32 so01 login[3530]: pam_mount: checking sanity of volume
record (test frgb)
Feb 22 12:02:32 so01 login[3530]: pam_mount: about to perform mount
operations
Feb 22 12:02:32 so01 login[3530]: pam_mount: information for mount:
Feb 22 12:02:32 so01 login[3530]: pam_mount: --------
Feb 22 12:02:32 so01 login[3530]: pam_mount: (defined by luserconf)
Feb 22 12:02:32 so01 login[3530]: pam_mount: user: schommer
Feb 22 12:02:32 so01 login[3530]: pam_mount: server: ntserver
Feb 22 12:02:32 so01 login[3530]: pam_mount: volume: test frgb
Feb 22 12:02:32 so01 login[3530]: pam_mount: mountpoint:
/home/schommer/mnt/test
Feb 22 12:02:32 so01 login[3530]: pam_mount: options:
Feb 22 12:02:32 so01 login[3530]: pam_mount: fs_key_cipher:
Feb 22 12:02:32 so01 login[3530]: pam_mount: fs_key_path:
Feb 22 12:02:32 so01 login[3530]: pam_mount: use_fstab: 0
Feb 22 12:02:32 so01 login[3530]: pam_mount: --------
Feb 22 12:02:32 so01 login[3530]: pam_mount: checking to see if
//ntserver/test frgb is already mounted at /home/schommer/mnt/test
Feb 22 12:02:32 so01 login[3530]: pam_mount: checking for encrypted
filesystem key configuration
Feb 22 12:02:32 so01 login[3530]: pam_mount: about to start building
mount command
Feb 22 12:02:32 so01 login[3530]: pam_mount: command: /usr/bin/smbmount
//ntserver/test frgb /home/schommer/mnt/test -o username=3Dschommer
Feb 22 12:02:32 so01 login[3676]: pam_mount: setting uid to user
schommer
Feb 22 12:02:32 so01 login[3676]: pam_mount: real and effective user ID
are 1001 and 1001.
Feb 22 12:02:32 so01 login[3676]: pam_mount: real and effective group ID
are 1001 and 1001.
Feb 22 12:02:32 so01 login[3530]: pam_mount: mount errors (should be
empty):
Feb 22 12:02:32 so01 login[3530]: pam_mount: pam_mount: setting uid to
user schommer
Feb 22 12:02:32 so01 login[3530]: pam_mount: pam_mount: real and
effective user ID are 1001 and 1001.
Feb 22 12:02:32 so01 login[3530]: pam_mount: pam_mount: real and
effective group ID are 1001 and 1001.
Feb 22 12:02:32 so01 login[3530]: pam_mount: Could not resolve mount
point frgb
Feb 22 12:02:32 so01 login[3530]: pam_mount: waiting for mount
Feb 22 12:02:32 so01 login[3530]: pam_mount: clean system authtok (0)
Feb 22 12:02:32 so01 login[3677]: pam_mount: setting uid to 0
Feb 22 12:02:32 so01 login[3677]: pam_mount: real and effective user ID
are 0 and 0.
Feb 22 12:02:32 so01 login[3677]: pam_mount: real and effective group ID
are 1001 and 1001.
Feb 22 12:02:32 so01 login[3530]: pam_mount: pmvarrun says login count
is 4
Feb 22 12:02:32 so01 login[3530]: pam_mount: done opening session
Feb 22 12:02:32 so01 login[3530]: (pam_unix) session opened for user
schommer by LOGIN(uid=3D0)
Feb 22 12:02:32 so01 login[3530]: pam_mount: user is schommer
Feb 22 12:02:32 so01 login[3530]: pam_mount: path to luserconf set to
/home/schommer/.pam_mount.conf
Feb 22 12:02:32 so01 login[3530]: pam_mount: reading options_allow...
Feb 22 12:02:32 so01 login[3530]: pam_mount: back from global readconfig
Feb 22 12:02:32 so01 login[3530]: pam_mount: going to readconfig user
Feb 22 12:02:32 so01 login[3530]: pam_mount: back from user readconfig
Feb 22 12:02:32 so01 login[3530]: pam_mount: real and effective user ID
are 0 and 0.
Feb 22 12:02:32 so01 login[3530]: pam_mount: checking sanity of volume
record (test frgb)
Feb 22 12:02:32 so01 login[3530]: pam_mount: about to perform mount
operations
Feb 22 12:02:32 so01 login[3530]: pam_mount: information for mount:
Feb 22 12:02:32 so01 login[3530]: pam_mount: --------
Feb 22 12:02:32 so01 login[3530]: pam_mount: (defined by luserconf)
Feb 22 12:02:32 so01 login[3530]: pam_mount: user: schommer
Feb 22 12:02:32 so01 login[3530]: pam_mount: server: ntserver
Feb 22 12:02:32 so01 login[3530]: pam_mount: volume: test frgb
Feb 22 12:02:32 so01 login[3530]: pam_mount: mountpoint:
/home/schommer/mnt/test
Feb 22 12:02:32 so01 login[3530]: pam_mount: options:
Feb 22 12:02:32 so01 login[3530]: pam_mount: fs_key_cipher:
Feb 22 12:02:32 so01 login[3530]: pam_mount: fs_key_path:
Feb 22 12:02:32 so01 login[3530]: pam_mount: use_fstab: 0
Feb 22 12:02:32 so01 login[3530]: pam_mount: --------
Feb 22 12:02:32 so01 login[3530]: pam_mount: checking to see if
//ntserver/test frgb is already mounted at /home/schommer/mnt/test
Feb 22 12:02:32 so01 login[3530]: pam_mount: checking for encrypted
filesystem key configuration
Feb 22 12:02:32 so01 login[3530]: pam_mount: about to start building
mount command
Feb 22 12:02:32 so01 login[3530]: pam_mount: command: /usr/bin/smbmount
//ntserver/test frgb /home/schommer/mnt/test -o username=3Dschommer
Feb 22 12:02:32 so01 login[3678]: pam_mount: setting uid to user
schommer
Feb 22 12:02:32 so01 login[3678]: pam_mount: real and effective user ID
are 1001 and 1001.
Feb 22 12:02:32 so01 login[3678]: pam_mount: real and effective group ID
are 1001 and 1001.
Feb 22 12:02:32 so01 login[3530]: pam_mount: mount errors (should be
empty):
Feb 22 12:02:32 so01 login[3530]: pam_mount: pam_mount: setting uid to
user schommer
Feb 22 12:02:32 so01 login[3530]: pam_mount: pam_mount: real and
effective user ID are 1001 and 1001.
Feb 22 12:02:32 so01 login[3530]: pam_mount: pam_mount: real and
effective group ID are 1001 and 1001.
Feb 22 12:02:32 so01 login[3530]: pam_mount: Could not resolve mount
point frgb
Feb 22 12:02:32 so01 login[3530]: pam_mount: waiting for mount
Feb 22 12:02:32 so01 login[3530]: pam_mount: checking sanity of volume
record (test frgb)
Feb 22 12:02:32 so01 login[3530]: pam_mount: about to perform mount
operations
Feb 22 12:02:32 so01 login[3530]: pam_mount: information for mount:
Feb 22 12:02:32 so01 login[3530]: pam_mount: --------
Feb 22 12:02:32 so01 login[3530]: pam_mount: (defined by luserconf)
Feb 22 12:02:32 so01 login[3530]: pam_mount: user: schommer
Feb 22 12:02:32 so01 login[3530]: pam_mount: server: ntserver
Feb 22 12:02:32 so01 login[3530]: pam_mount: volume: test frgb
Feb 22 12:02:32 so01 login[3530]: pam_mount: mountpoint:
/home/schommer/mnt/test
Feb 22 12:02:32 so01 login[3530]: pam_mount: options:
Feb 22 12:02:32 so01 login[3530]: pam_mount: fs_key_cipher:
Feb 22 12:02:32 so01 login[3530]: pam_mount: fs_key_path:
Feb 22 12:02:32 so01 login[3530]: pam_mount: use_fstab: 0
Feb 22 12:02:32 so01 login[3530]: pam_mount: --------
Feb 22 12:02:32 so01 login[3530]: pam_mount: checking to see if
//ntserver/test frgb is already mounted at /home/schommer/mnt/test
Feb 22 12:02:32 so01 login[3530]: pam_mount: checking for encrypted
filesystem key configuration
Feb 22 12:02:32 so01 login[3530]: pam_mount: about to start building
mount command
Feb 22 12:02:32 so01 login[3530]: pam_mount: command: /usr/bin/smbmount
//ntserver/test frgb /home/schommer/mnt/test -o username=3Dschommer
Feb 22 12:02:32 so01 login[3679]: pam_mount: setting uid to user
schommer
Feb 22 12:02:32 so01 login[3679]: pam_mount: real and effective user ID
are 1001 and 1001.
Feb 22 12:02:33 so01 login[3679]: pam_mount: real and effective group ID
are 1001 and 1001.
Feb 22 12:02:33 so01 login[3530]: pam_mount: mount errors (should be
empty):
Feb 22 12:02:33 so01 login[3530]: pam_mount: pam_mount: setting uid to
user schommer
Feb 22 12:02:33 so01 login[3530]: pam_mount: pam_mount: real and
effective user ID are 1001 and 1001.
Feb 22 12:02:33 so01 login[3530]: pam_mount: pam_mount: real and
effective group ID are 1001 and 1001.
Feb 22 12:02:33 so01 login[3530]: pam_mount: Could not resolve mount
point frgb
Feb 22 12:02:33 so01 login[3530]: pam_mount: waiting for mount
Feb 22 12:02:33 so01 login[3530]: pam_mount: clean system authtok (0)
Feb 22 12:02:33 so01 login[3680]: pam_mount: setting uid to 0
Feb 22 12:02:33 so01 login[3680]: pam_mount: real and effective user ID
are 0 and 0.
Feb 22 12:02:33 so01 login[3680]: pam_mount: real and effective group ID
are 1001 and 1001.
Feb 22 12:02:33 so01 login[3530]: pam_mount: pmvarrun says login count
is 5
Feb 22 12:02:33 so01 login[3530]: pam_mount: done opening session
-- snip --
the global configuration file of libpam-mount shows:
so01:~# cat /etc/security/pam_mount.conf
debug 1
mkmountpoint 1
luserconf .pam_mount.conf
options_allow nosuid,nodev,loop,encryption
smbmount /usr/bin/smbmount //%(SERVER)/%(VOLUME) %(MNTPT) -o
"username=3D%(USER)%(before=3D\",\" OPTIONS)"
-- snip --
greetings,
marcus schommer
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-1-686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=3DISO-8859-15)
Versions of packages libpam-mount depends on:
ii libc6 2.3.2.ds1-20 GNU C Library: Shared
libraries an
ii libglib2.0-0 2.6.2-1 The GLib library of C routin=
es
ii libssl0.9.7 0.9.7e-2 SSL shared libraries
ii mount 2.12-10 Tools for mounting and
manipulatin
ii zlib1g 1:1.2.2-3 compression library - runtim=
e
-- no debconf information
---------------------------------------
Received: (at 296417-close) by bugs.debian.org; 24 Feb 2005 17:24:35 +0000
>From [EMAIL PROTECTED] Thu Feb 24 09:24:35 2005
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1D4Mj5-0000Wd-00; Thu, 24 Feb 2005 09:24:35 -0800
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
id 1D4McL-0003Pk-00; Thu, 24 Feb 2005 12:17:37 -0500
From: Bastian Kleineidam <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.55 $
Subject: Bug#296417: fixed in libpam-mount 0.9.22-1
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Thu, 24 Feb 2005 12:17:37 -0500
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Source: libpam-mount
Source-Version: 0.9.22-1
We believe that the bug you reported is fixed in the latest version of
libpam-mount, which is due to be installed in the Debian FTP archive:
libpam-mount_0.9.22-1.diff.gz
to pool/main/libp/libpam-mount/libpam-mount_0.9.22-1.diff.gz
libpam-mount_0.9.22-1.dsc
to pool/main/libp/libpam-mount/libpam-mount_0.9.22-1.dsc
libpam-mount_0.9.22-1_i386.deb
to pool/main/libp/libpam-mount/libpam-mount_0.9.22-1_i386.deb
libpam-mount_0.9.22.orig.tar.gz
to pool/main/libp/libpam-mount/libpam-mount_0.9.22.orig.tar.gz
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Bastian Kleineidam <[EMAIL PROTECTED]> (supplier of updated libpam-mount
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Tue, 22 Feb 2005 18:32:45 +0100
Source: libpam-mount
Binary: libpam-mount
Architecture: source i386
Version: 0.9.22-1
Distribution: unstable
Urgency: low
Maintainer: Bastian Kleineidam <[EMAIL PROTECTED]>
Changed-By: Bastian Kleineidam <[EMAIL PROTECTED]>
Description:
libpam-mount - a PAM module that can mount volumes for a user session
Closes: 296417
Changes:
libpam-mount (0.9.22-1) unstable; urgency=low
.
* New upstream release.
* Dropped patches applied upstream, and updated all others.
* New patches:
- 29_crypto_compile_fix: add missing includes
- 31_no_ws_arg_split: support whitespace in command arguments
(Closes: #296417) - does not mount smb shares with whitespace
Files:
f59e1ca7e86298902b5198acfc2a65c6 669 admin extra libpam-mount_0.9.22-1.dsc
deb6d1b8bf8b0647b3b9c944d21f3c67 410614 admin extra
libpam-mount_0.9.22.orig.tar.gz
e7133703129d43a6bae3677e54eb6130 49382 admin extra
libpam-mount_0.9.22-1.diff.gz
7f8e62d7364a689897b6dedd30f360d1 102650 admin extra
libpam-mount_0.9.22-1_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
iD8DBQFCHghkeBwlBDLsbz4RAktBAJ9q2C8eDz1M2Yn4xbnZToV3iAcM6gCghAaR
NDSj+eUopiDuQwfU5FI+g5o=
=UBR/
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
