You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For a rsync backup, I need to have the reverse-mounted encrypted directory owned by a specific non-privileged user in order to limit access of the backup user.
It seems that adding the -force_owner option while reverse-mounting the plain directory does not have an effect, i.e. all the files in the encrypted dir have the same ownership of the plain files. Is this the expected behavior? The documentation does not specify if the two options are compatible.
My current workaround is to remount the encrypted dir on another mountpoint using bindfs, but I would like to avoid stacking filesystems one over the other if possible.
The text was updated successfully, but these errors were encountered:
For a rsync backup, I need to have the reverse-mounted encrypted directory owned by a specific non-privileged user in order to limit access of the backup user.
It seems that adding the -force_owner option while reverse-mounting the plain directory does not have an effect, i.e. all the files in the encrypted dir have the same ownership of the plain files. Is this the expected behavior? The documentation does not specify if the two options are compatible.
My current workaround is to remount the encrypted dir on another mountpoint using bindfs, but I would like to avoid stacking filesystems one over the other if possible.
The text was updated successfully, but these errors were encountered: