Repository navigation
1.10.0: portability matrix and disclosure timeline - #3
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.
Two documents that were measured but never published, plus a link from the coverage matrix.
PORTABILITY.md— the matrix behind "public PoC results vary by host": 17 measured cells on the same lab image, and what each one shows.memory_limitis not the gate —post_max_sizeis. At 512M/480 MB the chain runs the same because the body fits; at the default 8M the primitive never starts.N-1held.KeepAlive Onbreaks the chain outright (0/5) — the cheapest mitigation on the list, and it is not in PHP.display_errors=Offblocks exactly one thing: thelibphpleak. Primitive A and the chunk base survive.TIMELINE.md— the disclosure from 11 Aug to today, public sources plus our lab dates, marked. It is what makes claims checkable: the release moved from the 22nd to the 21st because of the CVE leak, and Chainguard shipped the fix six hours early, which explains exploitation attempts without a validated public PoC.Both in English and Spanish. No finding changes; the 9bie paragraph in the README now points at the matrix for the profile that was not reproduced here.