[Bug 1702529] Re: ACCESS_DENIED with symlinks within a root ("/") share

[Eric Desrochers]

yes, I do have a link (buildlog) :

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-xenial/xenial/amd64/g/gvfs/20170825_135452_c32a9@/log.gz

-- 
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/1702529

Title:
   ACCESS_DENIED with symlinks within a root ("/") share

Status in samba:
  Unknown
Status in samba package in Ubuntu:
  Fix Released
Status in samba source package in Trusty:
  Fix Committed
Status in samba source package in Xenial:
  Fix Committed
Status in samba source package in Zesty:
  Fix Committed

Bug description:
  [Impact]

   * In case of accessing directories chdir to it directly instead of
  its parent directory. This changes how dir symlinks are handled in
  root shares and leads to avoiding the ACCESS_DENIED ISSUE.

  [Test Case]

   1. Prepare smb server with a share:
  [rootshare]
     guest ok = yes
     path = /
     wide links = no
     follow symlinks = yes
   2. On the server:
  mkdir -p /srv/dir
  ln -s /srv/dir /srv/symdir.
   3. Connect from a client:
  smbclient -m smb3 //server/rootshare -c "cd srv\symdir; dir"

  [Regression Potential]

   * When accessing broken symlinks share's base directory is accessed.
  This however seems to be consistent with a pre-fix behavior.

  [Other Info]

  This fix is included in Samba 4.6.7 release so Artful and Debian both
  have it already.

  Original bug description:

  See Samba bug: https://bugzilla.samba.org/show_bug.cgi?id=12873 for
  more information and test case. Also view LP bug:
  https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1701073 for more
  information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/samba/+bug/1702529/+subscriptions