[Pkg-samba-maint] Bug#866823: Bug#866823: Bug#866823: samba: does not follow symbolic links

[Ritesh Raj Sarraf]

Hi Andrew,

This was just my initial conversation on the bug report. Usually, once
the conversation is concluded, the next gradual step is to file a bug
report upstream, either by the Package Maintainer in Debian or the bug
reporter. 

So that was something that may have followed up depending on the
outcome in this bug report.

And personally, my practice is to first file a bug report with the
Distribution maintainer, for multiple reasons.

* THey know better if there are any specific downstream deviations.
* They know better if this is a known issue
* They know better if this is a known (new) behavior.
* They know better what kind of information do each upstreams' usually
want.



On Mon, 2020-11-23 at 23:33 +1300, Andrew Bartlett wrote:
> I'm sorry, with snippets of smb.conf and vague references to a
> feature
> that is on by default (follow symlinks = yes is the default), it is
> really hard to know what exactly was working that is not working any
> more.
> 

Please find attached the smb.conf file. The only change from today is
the addition of 2 new settings.

wide links = yes
allow insecure wide links  = yes

And I'm not sure if "follow symlinks = yes" was the default and
effective in Debian. Because, when I first setup the shares, I had to
explicitly add the "follow symlinks = yes" attribute to get symlinks
followed.

> Also, upstream bugzilla.samba.org is probably a better place to raise
> concerns, nobody (else) here develops the code (and I do the AD DC)
> so
> it becomes message-passing at best.
> 
> When you are there, explain in painful detail exactly what did work,
> the smb.conf used in the past, and what now fails to work, including
> the full FS layout information.


-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
-------------- next part --------------
[global]
   workgroup = CHUTZPAH
   log file = /var/log/samba/log.%m
   max log size = 1000
   logging = file
   panic action = /usr/share/samba/panic-action %d
   server role = standalone server
   obey pam restrictions = yes
   unix password sync = yes
   passwd program = /usr/bin/passwd %u
   passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
   pam password change = yes
   map to guest = bad user
   usershare allow guests = yes

   allow insecure wide links  = yes

[EXDATA]
   comment = EXDATA
   browseable = yes
   follow symlinks = yes
   wide links = yes
   read only = no
   create mask = 0770
   directory mask = 0770
   path = /media/rrs/EXDATA
   #guest ok = yes

[4TBWD]
   comment = 4TBWD
   browseable = yes
   follow symlinks = yes
   wide links = yes
   read only = no
   create mask = 0770
   directory mask = 0770
   path = /media/rrs/4TBWD
   #guest ok = yes

[4TBWD_RO]
   comment = 4TBWD_RO
   browseable = yes
   follow symlinks = yes
   wide links = yes
   read only = yes
   create mask = 0770
   directory mask = 0770
   path = /media/rrs/4TBWD
   guest ok = yes

[TRANS]
   comment = BTRFS
   browseable = yes
   follow symlinks = yes
   wide links = yes
   read only = no
   create mask = 0770
   directory mask = 0770
   path = /home/rrs/Trans/

[homes]
   comment = Home Directories
   browseable = yes
   read only = no
   create mask = 0700
   directory mask = 0700
   valid users = %S

[printers]
   comment = All Printers
   browseable = no
   path = /var/spool/samba
   printable = yes
   guest ok = no
   read only = yes
   create mask = 0700

[print$]
   comment = Printer Drivers
   path = /var/lib/samba/printers
   browseable = yes
   read only = yes
   guest ok = no
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-samba-maint/attachments/20201123/f539ceea/attachment.sig>