Repository navigation
Bind OpenPGP dispositions to reviewed runtime payloads - #345
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.
Correction
The final Server scan correctly rejected three
GO-2026-5932occurrences after the authentication and machine-driver upgrades. Their original component releases already carry independently verified OpenPGP-absence dispositions forx/crypto v0.57.0; the Server still referenced only older module versions.This carries the reviewed disposition into the consumer without weakening the UNKNOWN/fixed-version gate. Before VEX is applied, every affected executable must match its exact reviewed path, module version and binary SHA256. An additional consumer, changed producer payload or new module version stops publication.
Validation
Normal required checks, final image scanning and deployment QA remain required.