LucidLink client supports 'chmod' and 'chown' unix commands.
File/Folder permissions are global, i.e. they will be shared and visible across all Unix LucidLink clients, connected to that file system. For example, if you set execute permissions for a file in Linux, the same file will still be executable in OSX or another Linux LucidLink client.
As a distributed file system, sharing owner and group of a file/folder across different LucidLink clients doesn't make much sense, unless all Unix users/groups are not "synced" across the whole file system, which would be very unusual requirement. For this reason, owner/group IDs are **per LucidLink client**. This means, that any user can change any other user's data, as long as it's connected via another LucidLink client.
By default (if the `chown` is not explicitly executed on a file/folder), LucidLink will report owner/group ID for all files and folders to be the owner/group ID of the user, that started LucidLink. In the general use-case, these permissions do not provide better security, they are for better user experience and for tools, which explicitly check and validate files/folders' permissions (e.g. working with `.pem` files) vs custom access control lists.
Article is closed for comments.