UnTar: skip the '.' archive root entry#91
Closed
mzihlmann wants to merge 1 commit into
Closed
Conversation
mzihlmann
force-pushed
the
permissions
branch
5 times, most recently
from
adfd360 to
f1971be
Compare
mzihlmann
force-pushed
the
permissions
branch
3 times, most recently
from
50265bf to
9c14ac3
Compare
mzihlmann
force-pushed
the
permissions
branch
2 times, most recently
from
a64b36f to
4c2fe88
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
mzihlmann
changed the title
Collaborator
Author
|
Reduced this to just the UnTar root-entry skip. The USER/RUN group handling moved to #840, where it is gated behind a feature flag. |
Collaborator
Author
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.
When untarring an archive whose root is
.(for example a build context tar),UnTarpassed the.entry toExtractFile, which resolves to the destination directory itself and reapplies the entry's mode and ownership onto it. Skipping the.entry leaves the destination directory untouched.