cp: do not descend into a destination subdirectory that is a symlink - #13624
Open
sylvestre wants to merge 2 commits into
Open
cp: do not descend into a destination subdirectory that is a symlink#13624sylvestre wants to merge 2 commits into
sylvestre wants to merge 2 commits into
Conversation
copy_direntry tested the destination with exists(), which resolves symlinks, so a destination entry that was itself a symlink to a directory looked like an existing directory and was descended into, writing the source subtree through the link and out of the destination tree. GNU refuses this. Treat a symlink at the destination as the non-directory it is. A symlinked directory named as the target itself stays allowed.
|
GNU testsuite comparison: |
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.
copy_direntry tested the destination with exists(), which resolves symlinks, so a destination entry that was itself a symlink to a directory looked like an existing directory and was descended into, writing the source subtree through the link and out of the destination tree. GNU refuses this.
Treat a symlink at the destination as the non-directory it is. A symlinked directory named as the target itself stays allowed.