-
Notifications
You must be signed in to change notification settings - Fork 789
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[release-1.35] Address CVE-2024-3727 #5521
[release-1.35] Address CVE-2024-3727 #5521
Conversation
Ephemeral COPR build failed. @containers/packit-build please check. |
Bump c/image to v5.30.1 and c/common to v0.58.3 to addresses: CVE-2024-3727 https://issues.redhat.com/browse/RHEL-35438 https://issues.redhat.com/browse/RHEL-35441 [NO NEW TESTS NEEDED] Signed-off-by: tomsweeneyredhat <tsweeney@redhat.com>
As the title says. Bump to Buildah v1.35.4 to address a few recent CVEs. [NO NEW TESTS NEEDED] Signed-off-by: tomsweeneyredhat <tsweeney@redhat.com>
8d456ff
to
c2926ea
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ignore packit failures.
- ELN failures I gotta take it up with ELN maintainers
- EL8 we don't care about
- EL9 failing on FIPS
/lgtm
/approve
/hold
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lsm5, TomSweeneyRedHat The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold cancel |
I guess if we need to ship this quick on C9S, we could maybe build without FIPS for a while. Don't know what else it would break though. cc @jnovy |
9bec740
into
containers:release-1.35
Btw. I'm still unable to build this in CentOS. |
Bump c/image to v5.30.1 and c/common to v0.58.3 to addresses:
CVE-2024-3727
https://issues.redhat.com/browse/RHEL-35438
https://issues.redhat.com/browse/RHEL-35441
What type of PR is this?
What this PR does / why we need it:
How to verify it
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?