FS#18529 - [smbclient] missing umount.cifs
Attached to Project:
Arch Linux
Opened by Idares (Idares) - Tuesday, 02 March 2010, 15:32 GMT
Last edited by Tobias Powalowski (tpowa) - Friday, 05 March 2010, 18:23 GMT
Opened by Idares (Idares) - Tuesday, 02 March 2010, 15:32 GMT
Last edited by Tobias Powalowski (tpowa) - Friday, 05 March 2010, 18:23 GMT
|
Details
Description:
/sbin/umount.cifs does not exist after upgrading smbclient to version 3.5.0-1 Additional info: package version: smbclient-3.5.0-1 There is new configure option '--with-cifsumount' in samba 3.5.0. |
This task depends upon
Closed by Tobias Powalowski (tpowa)
Friday, 05 March 2010, 18:23 GMT
Reason for closing: Fixed
Additional comments about closing: smb legacy will not be implemented
Friday, 05 March 2010, 18:23 GMT
Reason for closing: Fixed
Additional comments about closing: smb legacy will not be implemented
sed -i 's|#define CIFS_LEGACY_SETUID_CHECK 0|#define CIFS_LEGACY_SETUID_CHECK 1|' ../client/mount.cifs.c
This functionality was introduced in Samba 3.5.0, from description:
/*
* By default, mount.cifs follows the conventions set forth by /bin/mount
* for user mounts. That is, it requires that the mount be listed in
* /etc/fstab with the "user" option when run as an unprivileged user and
* mount.cifs is setuid root.
*
* Older versions of mount.cifs however were "looser" in this regard. When
* made setuid root, a user could run mount.cifs directly and mount any share
* on a directory owned by that user.
*
* The legacy behavior is now disabled by default. To reenable it, set the
* following #define to true.
*/
#define CIFS_LEGACY_SETUID_CHECK 0
And now, some applications like smb4k does not work properly. My line enable legacy functionality, and, I think this is good idea for first time. I will report aboud this func to smb4k maintainer.