Repository navigation
Verify BAR static ELF manifest before image load - #1035
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
1 participant
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.
The BAR controller previously retained hashes for required image outputs without verifying the producer’s static ELF dependency inventory. It now requires bounded
STATIC-ELF.jsonand checks its root identities, dependency graph, file hashes and lookup aliases against the effective OCI filesystem after whiteouts, before any load. The result records static correspondence separately from loaded ABI acceptance.Validation: 21 BAR controls passed in 97.44 seconds; 12 archive, 24 common and 45 SC2 controls also passed. The first BAR control run exceeded its original 120-second limit; that failure is retained. Reusing synthetic source selection for independent archive variants reduced the revised run, but it still exceeds the documented 60-second warm target. Original streams and outcomes are retained. No local compiler, loader, engine or image ran. Independent exact-head source review passed; required hosted checks remain a delivery gate.
The five-path change preserves resource admission, original clocks, stores, capture/cleanup and SC2 behavior. The archive test change updates only its maintained entrypoint hash. Related: #1032. Full image qualification and the named old-writer/NVMe supplier hold remain open.