[Bug 1675698] Re: Cannot access anything under a subdirectory if symlinks are disallowed
Heiko Lechner
1675698 at bugs.launchpad.net
Mon Mar 27 07:52:56 UTC 2017
Downgraded to 4.3.8 until a fix is offered
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1675698
Title:
Cannot access anything under a subdirectory if symlinks are disallowed
Status in samba:
Unknown
Status in samba package in Ubuntu:
Confirmed
Status in samba source package in Precise:
Confirmed
Status in samba source package in Trusty:
Confirmed
Status in samba source package in Xenial:
Confirmed
Status in samba source package in Yakkety:
Confirmed
Status in samba source package in Zesty:
Confirmed
Status in samba package in Debian:
Confirmed
Bug description:
After upgrading to 4.3.11+dfsg-0ubuntu0.14.04.6, some of my shares
broke in a curious way. The affected shares have `follow symlinks =
no`; the ones with `follow symlinks = yes` aren't affected AFAICT.
Allowing symlinks on one of the affected shares mitigates the issue
for that share.
The issue is that access to anything under a direct subdirectory of
the share doesn't work. I can create a directory in `\\srv\share`,
e.g. `\\srv\share\foo`, but I can't create any files or directories
inside it, e.g. creating `\\srv\share\foo\bar` ends up with error 50
(The request is not supported). Attempts to access existing files or
directories at this level produce error 59 (An unexpected network
error occured).
The log at level 2 says:
```
../source3/smbd/vfs.c:1298(check_reduced_name)
check_reduced_name: Bad access attempt: branches is a symlink to foo/bar
```
... or:
```
../source3/smbd/vfs.c:1298(check_reduced_name)
check_reduced_name: Bad access attempt: . is a symlink to foo
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/samba/+bug/1675698/+subscriptions
More information about the foundations-bugs
mailing list