-
Notifications
You must be signed in to change notification settings - Fork 328
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
Extended attributes can not be set on file without write permissions #208
Comments
TomasKorbar
added a commit
to TomasKorbar/rsync
that referenced
this issue
Aug 19, 2021
When we need to set extended atributes of file which does not allow write then temporarily add write permission and after attributes are set, remove it again. Resolves RsyncProject#208
PR is still WIP. |
TomasKorbar
added a commit
to TomasKorbar/rsync
that referenced
this issue
Aug 23, 2021
When we need to set extended atributes of file which does not allow write then temporarily add write permission and after attributes are set, remove it again. Resolves RsyncProject#208
Alright PR is now ready for review. It passes our usecase and all tests from testsuite are passing. |
WayneD
added a commit
that referenced
this issue
Sep 26, 2021
* Eventually add write permission when setting extended attributes When we need to set extended atributes of file which does not allow write then temporarily add write permission and after attributes are set, remove it again. Resolves #208 Co-authored-by: Wayne Davison <wayne@opencoder.net>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi Wayne,
recently we encountered the old issue with rsync not being able to set extended file attributes
as non-root user. I am trying to find approach which could fix this (fake-super work-around unfortunately
does not work for us).
Would you be ok with function set_xattr checking whether the file has write permission and if not then temporarily adding it?
After the attributes are set, we can set the permissions back.
Reproducer:
The text was updated successfully, but these errors were encountered: