-
-
Notifications
You must be signed in to change notification settings - Fork 32.5k
gh-130577: tarfile now validates archives to ensure member offsets are non-negative #137027
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
…ets are non-negative
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's rather sad that the number format used within tar files even explicitly allows a way to express negative values. is there even a use case for that in the file format(s)?
Please cherry pick this commit to your branch (mispaste fixed): aa57b01 we don't want a whatsnew entry for this; whats new is for major features not bugfixes. a whatsnew entry makes backporting a chore (thus me removing the auto-backport labels for now) (github is refusing to let me push changes to your branch. Please always allow maintainers to push edits to PR branches.) |
(corrected mispasted commit link above) |
I enabled the allow edits to avoid any further issues and I cherry-picked the commit from your personal fork. |
By the way, thanks for the clarifications on the process 👍 |
tarfile.StreamError: seeking backwards is not allowed
due to unskipped block with bad checksum #130577📚 Documentation preview 📚: https://cpython-previews--137027.org.readthedocs.build/