Skip to content
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

jwe: limit maximum output from decompressing #106

Merged
merged 1 commit into from Mar 7, 2024
Merged

Conversation

jsha
Copy link
Collaborator

@jsha jsha commented Mar 7, 2024

No description provided.

@jsha jsha requested a review from mcpherrinm March 7, 2024 19:09
Copy link
Collaborator

@mcpherrinm mcpherrinm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have reviewed this and I think it's good:

One thing I did consider is that if int64(len(input)) is large, then 10x it could overflow. But having an input that large isn't possible, as it wouldn't fit on system memory in any system. We'd cap at 250_000 in that case anyways, as it would be larger than a negative overflowed value.

@jsha jsha merged commit f4c051a into main Mar 7, 2024
4 checks passed
@jsha jsha deleted the limit-decompress branch March 7, 2024 19:46
jsha added a commit that referenced this pull request Mar 7, 2024
jsha added a commit that referenced this pull request Mar 7, 2024
Backport from #106.

Note that there was a merge conflict on the CHANGELOG and I decided to
just accept all the v4 entries. It's okay for the v3 branch's CHANGELOG
to also talk about v4 releases. I'll send a separate PR updating the v4
CHANGELOG to include v3.0.3.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants