Hi, I discovered that it's not possible to run 'wide links' and 'unix
entensions' at the same time - there are source-level blockers in place
that will disable wide links and write a log entry. I traced this to
https://bugzilla.samba.org/show_bug.cgi?id=7104 and
http://www.samba.org/samba/news/symlink_attack.html ...
However, I run a private home LAN server that already exposes / (root)
as a share to all authenticated (and unauthenticated) clients. Therefore
this issue is irrelevant to me. Furthermore, I want to organize some
per-user directories (~/public_html for www, ~/storage for large files,
and so on) in a separate location, and I can't do this without wide
links. The restriction kills off my usage scenario.
When the abovementioned 'security' fixes were done, why weren't the
developers content with just changing the defaults, and maybe printing a
warning on startup? Why did they add this restriction without a way to
turn it off? Should I file a bugreport to have these blockers removed?
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
