The tool "smbumount" required by tl-umount-all-cifs does not seem to exist on RHEL6 (and perhaps other distributions). This makes tl-umount-all-cifs useless on these platforms.
Also, tl-mount-cifs requires either smbmount or mount.cifs - smbmount is not provided on RHEL6 (and perhaps other distributions), and mount.cifs is no longer shipping with a sticky bit. This means that tl-mount-cifs is probably useless on these platforms too.
It looks like "mount" is actually shipping with a sticky bit, although I'm not sure this helps us. We should investigate some possible solutions to this.
It seems to be even worse. Apparently, with newer versions of mount.cifs, ordinary users cannot mount even if the binary is setuid root, unless there's a hardcoded path in /etc/fstab. See https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/657900 .
One solution could be http://repo.or.cz/w/usmb.git . Unfortunately it requires options to go into a config file .usmb.conf right now.
One solution could be to switch to a FUSE solution.
(In reply to comment #5)
> One solution could be to switch to a FUSE solution.
This is also recommended by the cifs-utils release notes:
cifs-utils (2:4.0-1) unstable; urgency=low
* As of this version, the mount.cifs binary is no longer setuid due to
upstream concerns about the audit status of this code. As a consequence,
users will no longer be able to run mount.cifs directly to mount shares
unless mount points have been individually configured in /etc/fstab with
the "user" mount option.
Sites that require their users to retain the ability to mount arbitrary
CIFS shares without system-level configuration may want to consider using
the fusesmb package instead.
-- Steve Langasek <email address hidden> Sun, 28 Feb 2010 16:07:14 -0800
The fact that it has been broken for so long suggests that it isn't really used. So we should consider just removing this.
*** Bug 6107 has been marked as a duplicate of this bug. ***
Everything regarding this tool should now be removed.
Not adding any release notes given that this hasn't actually worked in a decade. So no users should be affected by this change.
This seems to be completely removed now!