Allow tilde in zip entry names #391
Merged
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.
Use
absolute_path
rather thanexpand_path
to allow tilde to pass through unchanged. Otherwise, we try to expand it to a home directory.For example, a zip containing a file named
~tilde~
caused this error on extraction:because it interpreted
~tilde~
as "get me the path to the home directory of the usertilde~
.An entry name containing
~
should still be considered 'safe', provided that the user doesn't use it in a shell context where the~
would again be expanded.This was introduced in #376 .
Thanks to @mmazour for catching this.