fix for archiving long paths that have path components starting with ".." crossing the 100-character mark #390
Conversation
This file contains 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
…ith .. at 100-character mark his test checks very particular scenario where path component starting with ".." of a long path gets split at 100-byte mark so that ".." goes into header and gets interpreted as parent dir (and rejected).
This is a fix for very specific scenario where a path component starting with ".." of a long path gets split at 100-byte mark so that ".." goes into header and gets interpreted as parent dir (and rejected). See tests for repro of the issue.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The gnu tar supports arbirary path length by putting path truncated to standard 100 chars into the header and the rest is appended to contents.
tar-rsvalidates that no path components should be exactly ".." but in this case when a component starting with ".." (for example file named "..some_file") gets truncated after 2 characters we hit this validation and can't tar such file.I have verified that gnu
tarcommand can handle such paths and actually puts truncated..in the header. This pull request makestar-rsbehave the same.See tests for repro of the issue.
(I think the code for handling this special case is quite ugly - I'd appreciate suggestions for making it better)