Repository navigation
fix(s130): openssl-libs justifications re-pinned to Red Hat's 3.5.8-2 rebuild - #130
Merged
Merged
Conversation
… rebuild Signed-off-by: Ayla Croft <aylacroft@proton.me>
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.
Red Hat shipped a rebuild of
openssl-libs(3.5.8-1.el9_8to3.5.8-2.el9_8) today. The image build runsdnf upgradeagainst the installroot, so it picked the rebuild up, and theimageworkflow went red on every branch built after it (#126, #123, #124):The scan still reports both as not fixed in the rebuild, and the justification's reasoning is about the image, not the package build: nothing in the image links
libssl.so.3, and both flaws are in libssl. So the two rows move to the new build; their text is unchanged, and the comment above them records the re-pin.Verified:
mix test test/mix/tasks/trinity_image_findings_test.exs, 12 passed. Theimagerun on this PR is the real check.Note for later: because the build upgrades from the live repositories, any Red Hat rebuild of a justified package will do this again. Keying rows on the exact build is deliberate (AC4 catches stale rows), so this is the expected cost, not a defect.