Repository navigation
Consume verified Ubuntu security backports in the final runtime - #5
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.
Update only already installed Ubuntu runtime packages from the digest-pinned, build-only security bundle. Preserve the compiler stage, package set, existing coreutils provider and configuration. Keep the original complete Trivy report and bind the actual image SBOM/installation receipt to the immutable producer checksums before native exact-package OpenVEX interpretation.
The bundle source/native suites and real GNU/uutils installation gates passed. Its original producer is Server commit 59f4ec1f31e510361c4635023c08fcf2a2b2133c (run 40138193717), immutable digest sha256:2742a3d429e4e14bc587f6dedc51ded4246cf90bbaedcd86c67d0885e32a6f2a. Anonymous full-output readback and provenance signature verification also passed. Original SBOM bytes are valid CycloneDX; completion of its missing SBOM attestation is still required before release. The original failed publication run is preserved.
Run the existing affected build, runtime, SBOM and security gates. No scanner exclusions, pending-finding ledgers, compiler inputs or unrelated workflows are weakened. No production deployment or runtime patch.