Feature Overview
It's inconvenient to end-users for MS to publish multiple .efiauth2 files for each of the SignedByKEK2011 subfolders, because having an unknown number of DBX files requires someone to write an automation script to crawl the GitHub folder.
I thought the point was to have one file which could be downloaded, compared against, or applied to the host. If new EFI hashes are to be published, a new consolidated DBX file should be provided, instead of a set of side by side files.
Solution Overview
In future DBX updates, consolidate the SignedByKEK2011 efiauth2 files into a single file (by architecture) provided in the repro
dbx_${Arch}_Legacy.efiauth2
Alternatives Considered
No response
Urgency
Medium
Are you going to implement the feature request?
No
Do you need maintainer feedback?
No maintainer feedback needed
Anything else?
No response
Feature Overview
It's inconvenient to end-users for MS to publish multiple .efiauth2 files for each of the SignedByKEK2011 subfolders, because having an unknown number of DBX files requires someone to write an automation script to crawl the GitHub folder.
I thought the point was to have one file which could be downloaded, compared against, or applied to the host. If new EFI hashes are to be published, a new consolidated DBX file should be provided, instead of a set of side by side files.
Solution Overview
In future DBX updates, consolidate the SignedByKEK2011 efiauth2 files into a single file (by architecture) provided in the repro
dbx_${Arch}_Legacy.efiauth2
Alternatives Considered
No response
Urgency
Medium
Are you going to implement the feature request?
No
Do you need maintainer feedback?
No maintainer feedback needed
Anything else?
No response