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

[Eric Desrochers]

The 2nd run of "gvfs [xenial/ppc64el]" passed but "gvfs [xenial/amd64]"
still fails as follow :

FAILED (failures=3, errors=1)
=== command failed, showing Samba log files ===
--- /var/log/samba/log.nmbd ---
[2017/08/25 13:53:56.757205,  0] ../lib/util/become_daemon.c:135(daemon_status)
  STATUS=daemon 'nmbd' : No local IPv4 non-loopback interfaces available, waiting for interface ...NOTE: NetBIOS name resolution is not supported for Internet Protocol Version 6 (IPv6).
--- /var/log/samba/log.smbd ---
[2017/08/25 13:53:56.815267,  0] ../lib/util/become_daemon.c:124(daemon_ready)
  STATUS=daemon 'smbd' finished starting up and ready to serve connections
autopkgtest [13:54:38]: test integration: -----------------------]
autopkgtest [13:54:38]: test integration:  - - - - - - - - - - results - - - - - - - - - -
integration          FAIL non-zero exit status 1
autopkgtest [13:54:39]: @@@@@@@@@@@@@@@@@@@@ summary
integration          FAIL non-zero exit status 1
Exit request sent.
Creating nova instance adt-xenial-amd64-gvfs-20170825-134910 from image ubuntu/ubuntu-xenial-daily-amd64-server-20170822-disk1.img (UUID bbd67b9f-5714-41ab-8072-a4dfc1ad85d5)...

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