Cannot access anything under a subdirectory if symlinks are disallowed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
samba |
Unknown
|
Unknown
|
|||
samba (Debian) |
Fix Released
|
Unknown
|
|||
samba (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Precise |
Fix Released
|
High
|
Marc Deslauriers | ||
Trusty |
Fix Released
|
High
|
Marc Deslauriers | ||
Xenial |
Fix Released
|
High
|
Marc Deslauriers | ||
Yakkety |
Fix Released
|
High
|
Marc Deslauriers | ||
Zesty |
Invalid
|
Undecided
|
Unassigned |
Bug Description
After upgrading to 4.3.11+
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\
The log at level 2 says:
```
../source3/
check_
```
... or:
```
../source3/
check_
```
CVE References
Changed in samba (Ubuntu Precise): | |
status: | New → Confirmed |
Changed in samba (Ubuntu Trusty): | |
status: | New → Confirmed |
Changed in samba (Ubuntu Xenial): | |
status: | New → Confirmed |
Changed in samba (Ubuntu Yakkety): | |
status: | New → Confirmed |
Changed in samba (Ubuntu Precise): | |
importance: | Undecided → High |
assignee: | nobody → Marc Deslauriers (mdeslaur) |
Changed in samba (Ubuntu Trusty): | |
importance: | Undecided → High |
assignee: | nobody → Marc Deslauriers (mdeslaur) |
Changed in samba (Ubuntu Xenial): | |
importance: | Undecided → High |
Changed in samba (Ubuntu Yakkety): | |
importance: | Undecided → High |
Changed in samba (Ubuntu Xenial): | |
assignee: | nobody → Marc Deslauriers (mdeslaur) |
Changed in samba (Ubuntu Yakkety): | |
assignee: | nobody → Marc Deslauriers (mdeslaur) |
Changed in samba (Ubuntu Zesty): | |
status: | New → Confirmed |
Changed in samba (Debian): | |
status: | Unknown → Confirmed |
Changed in samba (Ubuntu Zesty): | |
status: | Confirmed → Invalid |
Changed in samba (Debian): | |
status: | Confirmed → Fix Committed |
Changed in samba (Debian): | |
status: | Fix Committed → Fix Released |
Among the clients I tested with are Windows 10 (current stable -- AU) and Windows Server 2012 R2.