Skip to content
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

sbat: Add grub.peimage,2 to latest (CVE-2024-2312) #651

Merged
merged 1 commit into from Apr 9, 2024

Conversation

julian-klode
Copy link
Collaborator

Add the previous latest level to the switch for automatic.

Add the previous latest level to the switch for automatic.

Signed-off-by: Julian Andres Klode <julian.klode@canonical.com>
@julian-klode
Copy link
Collaborator Author

I guess to note:

  • This only affects Debian testing, unstable, Ubuntu mantic and the in-development noble
  • I've not bumped the default previous level, but recorded the previous latest level as a possible previous one

@julian-klode
Copy link
Collaborator Author

There's a question if we should also bump that latest to grub,4 now and drop the grub,debian entry. It's been what, 3 months now? We should do it before we get another round of CVEs and need to bump grub again, otherwise grub is going to be at grub,3 in previous and grub,5 in latest which would be messy.

@kukrimate
Copy link

I think latest should be "grub,4".

I think ideally latest should have been "grub,4" at the time of the 15.8, it would make sense that the actually secure revocations at the time of a specific shim release are always available as an opt in. In this case it made sense for people not affected by the NTFS CVE but still.

@vathpela
Copy link
Contributor

vathpela commented Apr 9, 2024

This looks good to me, as would updating to grub,4 and removing grub.debian in a different PR.

@vathpela vathpela merged commit 63edf92 into rhboot:main Apr 9, 2024
21 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants