-
Notifications
You must be signed in to change notification settings - Fork 313
Protection Against Zip Bombs #193
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
Comments
There is no such protections. |
What kind of protection would you expect? You can check size of each entry in zip file before unpacking. IMHO It should be sufficient but maybe you see problem here? |
^ And for the avoidance of doubt, "Currently" there means "before #403". |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there a way to protect against zip bombs? Are there limits where extraction is stopped? Can we configure limits? Can we do that at extraction-time by ourselves?
I cannot find anything about that in the documentation.
The text was updated successfully, but these errors were encountered: