Because misconfigured symlinks can be a security exposure, discussing
symlinks requires a little background:
If the client is Linux client, Samba server by default reports a symlink
as a symlink not as a directory. The Linux client can get information
on the symlink and follow it. Symlinks from within a network export
(share) to paths outside of the share, especially absolute paths (e.g.
like /etc/passwd) are usually a bad idea, but there are cases where they
may be useful.
If you want to follow symlinks on the server, rather than have the client
follow symlinks. You can turn off the Unix Extensions any of three ways:
1) "unix extensions = no" in the server smb.conf file
or
2) turning them off on the client before mount
echo 0 > /proc/fs/cifs/LinuxExtensionsEnabled
or
3) turning them off on the mount (cifs 1.50 or later, probably not in your
kernel)
mount -t cifs //server/share /mnt -o nounix
Also note that symlink following on the server can be disabled by
"follow symlinks = no" in the server's smb.conf (rarely needed)
I don't think behavior on the client side has changed in a while here
(other than the new mount option "nounix")
--
Mount with smbfs treats symlinks invalid
https://bugs.launchpad.net/bugs/134716
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
