Fix host UID/GID leakage in copyFileToContainer TAR entries#11929
Open
Gautam-aman wants to merge 1 commit into
Open
Fix host UID/GID leakage in copyFileToContainer TAR entries#11929Gautam-aman wants to merge 1 commit into
Gautam-aman wants to merge 1 commit into
Conversation
Author
|
This revives the approach from #11488, which was |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #11487
When copyFileToContainer copies a MountableFile,
TAR entries may carry host UID/GID values into
the container.
On rootless Docker setups these IDs may be
unmapped, causing permission and ownership issues.
This change normalizes TAR entry ownership to
uid=0 and gid=0 and adds a regression test.