Repository navigation
Update OpenStrata to 0.23.20 and guard bundled SOG metadata - #48
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
openstrata.ci.yaml.meta.jsonbefore allocating or inflating the entry in bundled SOG. Full and metadata-only reads reportGSSOG-E016when it exceeds 4 MiB.Why?
The v0.6.0 roadmap calls for hostile-input coverage. The ZIP reader previously attempted extraction under its general per-entry budget before applying the smaller metadata budget. OpenStrata 0.23.20 also fixes how the viewer finds the managed stage for the selected target. OpenStrata release notes
Validation
PYTHONUTF8=1, including the resolver and benchmark suites. The new oversized-metadata fixture reproducedGSSOG-E004before the fix and passes with the expectedGSSOG-E016afterward.ost plugin test --workspace --up-to 5and the corresponding--from-packagerun passed for PLY, SPZ, and SOG. Two aggregate packaging runs produced the same SHA-256.ost ci validate, workflow regeneration, release preflight, andclang-formatchecks passed. All three new fixtures regenerated byte-for-byte.Checklist
Reviewer notes
Hosted verification for the new pin will run on this PR.