Created attachment 1226 [details] smbd warning message The attached warning message is shown if a share in samba has a wide link in place. wide links = yes is written into the smb.confg file by samba.cgi but smb1 unix extensions = yes by default which means that if there is a symlink in a samba share that points outside of the share directory tree then that symlink will never be shown. This occurred around 3 years ago when the samba wui page was simplified. The wide links = yes was added but the smb1 unix extensions (originally synonymous with unix extensions) was not specified meaning that the default value was used which is yes.
Patch will be created that adds smb1 unix extensions = no to the smb.conf file. This has been confirmed to work on my vm testbed system with samba installed.
This issue was flagged up in a forum post on another samba related issue. https://community.ipfire.org/t/samba-performance-4-18-1/10086
Patch has been created and tested and submitted to the dev mailing list and patchwork https://lists.ipfire.org/pipermail/development/2023-July/016191.html https://patchwork.ipfire.org/project/ipfire/patch/20230726210359.24473-1-adolf.belka@ipfire.org/
I am not sure if this is free from any side-effects if we change defaults for shares. However, the UNIX extensions have always been causing trouble, so let's turn them off and be safe. IPFire is not a fileserver. If people run into trouble, they might want to look at an alternative or (re-)enable this on a per-share basis.
patch has been merged https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=cee7ddb66c22bfdd7a0dce18617f64b34d7794e7
https://blog.ipfire.org/post/ipfire-2-27-core-update-179-is-available-for-testing
Verified that message about wide links = yes clashing with smb1 unix extensions = yes is no longer seen.
https://blog.ipfire.org/post/ipfire-2-27-core-update-179-released