This repository has been archived by the owner on Jul 4, 2023. It is now read-only.
Properly identify POSIX uncompressed tars #12011
Closed
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 first 6 bytes are not enough to identify POSIX
uncompressed tars (257 bytes offset), so changed
the magic_bytes to read the first 262 bytes.
This is almost the same as #10226. Can be tested with a POSIX tar with this (dummy) formula: