Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

force_owner not working in reverse mode #809

Open
m4rc0d1 opened this issue Dec 1, 2023 · 0 comments
Open

force_owner not working in reverse mode #809

m4rc0d1 opened this issue Dec 1, 2023 · 0 comments

Comments

@m4rc0d1
Copy link

m4rc0d1 commented Dec 1, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants