Problems when syncing from Windows to Synology NAS

[calmh (Jakob Borg)]

You discovered that chmod on Synology breaks ACL inheritance, which is annoying. Our “chmod” on Windows (effectively, setting or unsetting the read only bit) does not break ACL inheritance, as far as I know. Hence,

@calmh

ACLs take effect as usual.

[xarx]

For completeness, in relation to my previous post Problems when syncing from Windows to Synology NAS :

Synology privileges seem to be controlled exclusively by ACLs. If a file/directory has no assigned ACL, it deduces the ACL from the unix “rwx” flags. But in case ACL is assigned, the unix rights are completely ignored. They may even not correspond to the actual ACL privileges. E.g. after creating a new file in the internal text editor:

$ls -le aa
----------+ 1 sc-syncthing syncthing 1507328 Feb 10 12:29 aa
         [0] group:administrators:allow:rwxpdDaARWc--:---- (level: 4)
         [1] group:sc-syncthing:allow:rwxpdDaARWc--:---- (level: 4)

unix rights are not filled in at all!

The Synology privilege system is not bad, but it is totally incompatible with unix-like rights. Even Windows are more compatible than Synology: if you want to make a file read-only on Synology, you have to edit the ACL; on Windows, there is a read-only flag.

If it is possible to distinguish Synology as a platform when building Syncthing, Ignore Privileges should be always checked here. When Privileges are not ignored, reading unix privileges is unreliable from the perspective of ST.