This program is not installed setuid root - "user"
CIFS mounts not supported
samba bug at redhat: Race condition by mount (mount.cifs) operationsNetwork addresses can only have two parts
//IPaddress (or PCname)and/Sharedfoldername (no more slash and parts)//IPaddress/sharename
Bug#572691 at debian: samba shares can no longer be mounted by user
MITRE has rejected the use of CVE-2009-3297 because it was used for samba, ncpfs, and fuse when it should only have been used for Samba.
Instead, new CVEs have been assigned as follows:
This issue does not affect Red Hat Enterprise Linux 4 and 5 by default as mount.cifs is not provided with the setuid bit enabled. If a user has turned on the setuid bit (via 'chmod +s /sbin/mount.cifs'), they would be affected by this issue and can workaround the problem by removing the setuid bit.
# ls -la /sbin/mount.cifs
-rwxr-xr-x 1 root root 27716 Mar 24 08:06 /sbin/mount.cifs
# cat /etc/fstab # (remark: only last line given)
//smbserver/share /mnt/smb_share smbfs user,noexec,noauto 0 0
But as normal user:
a) not-having mount.cifs setuid:
$ mount /mnt/smb_share
/sbin/mount.cifs: not installed setuid - "user" CIFS mounts not
b) when having setuid:
$ mount /mnt/smb_share
This mount.cifs program has been built with the ability to run as a setuid root program disabled.
mount.cifs has not been well audited for security holes. Therefore the Samba team does not recommend installing it as a setuid root program.
So two observations:
1 - The hints in NEWS (at least the fstab hint) won't work. (Or you should be
2 - The programm actually tells me "first do that" and after doing that it
tells me "you cannot do that". That should be probably filed as another bug.
(Well, as it is kind-of already filed: #576314 New upstream 4.2 version
available, the whole problem should be gone soon...)
SuSE bug report: https://bugzilla.novell.com/show_bug.cgi?id=618877
They say it's fixed and an update has been released. Try a full online update and see if it really is fixed
# mount //138.XXX.XXX.X/folder/Documents /home/folder/Documents/ -t cifs -o username=username,password=password,uid=1000,gid=1000
If the mount works with command line then I think the network is coming on line after the mounts are run according to fstab. If the network is a few seconds slower than the execution of fstab, the mount will fail.
So create a file called after.local
and put this code in it:
#! /bin/sh mount -a
and make it executable with this command:
sudo chmod a+x /etc/init.d/after.local
Reference: A permanent mount fails at boot time -- Is something delaying the network at boot time?
remotetarget dir cifs options...credentials 0 0