-
-
Notifications
You must be signed in to change notification settings - Fork 138
use chown on rsync to /data and /config directories #517
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
base: master
Are you sure you want to change the base?
Conversation
|
I am a bot, here are the test results for this PR:
|
b8d8aaa to
41cf540
Compare
|
I am a bot, here are the test results for this PR:
|
|
I am a bot, here are the test results for this PR:
|
|
This pull request has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
The lsiown command explicitly avoids touching symlinks, allowing root owned symlinks to bleed into PUID/PGID controlled areas. Use the chown arguments when using rsync to copy files to /data and /config to prevent creating symlinks with root permissions. Signed-off-by: Randolph Sapp <[email protected]>
41cf540 to
f850beb
Compare
|
I am a bot, here are the test results for this PR:
|
|
Forgive the ping, but @thespad is there any feedback regarding this? |
|
I've found that this is a requirement to silence log messages like the following: |
|
I am a bot, here are the test results for this PR:
|
|
I am a bot, here are the test results for this PR:
|
Description:
The lsiown command explicitly avoids touching symlinks, allowing root owned symlinks to bleed into PUID/PGID controlled areas.
Use the chown arguments when using rsync to copy files to /data and /config to prevent creating symlinks with root permissions.
Benefits of this PR and context:
Prevents creating symlinks as root, which the fpm or host user will not be able to remove/replace as needed.
How Has This Been Tested?
I used the modified commands to remove existing invalid symlinks from my deployment.
Source / References:
N/A