On Wed, Dec 31, 2025 at 11:26:03AM -0800, Adam Williamson wrote: > On Wed, 2025-12-31 at 17:31 +0000, Gary Buhrmaster wrote: > > On Mon, Dec 22, 2025 at 4:53 PM Mateus Rodrigues Costa > > <[email protected]> wrote: > > > > > 2) We are close to January, what's keeping us from receiving shims > > > signed with the new 2023 certs? It seems Neal said that Microsoft > > > would start signing with the new certs in October of last year. Am I > > > missing something? > > > > I don't think the shims (grub, systemd-boot, ??) > > have needed to be reissued (and re-signed) > > for quite some time, so I it just did not happen > > (yet). I believe for Fedora the latest codes > > (16.1?) are in the process of being validated > > (and, for what is probably obvious reasons, > > the number of people who are authorized to > > work the process is almost certainly going > > to be extremely limited). > > 16.1 is already signed for Fedora[0] and is in stable for F41 and F44. > It's in testing for F42 and F43, at least according to the tags. I > don't remember what's going on there, honestly. We might have just > forgotten about it? Kevin? Peter?
I didn't tag it into stable updates because there was a user with a issue with it on the test list and I never got any ack that that was addressed or didn't matter. https://forge.fedoraproject.org/releng/tickets/issues/13050 was closed, but they are not tagged into stable (yet). (I reopened it). kevin -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
