Skip to content

Fix PEM certificate handling for secure boot defaults - #476

Open
CHEA Oudomrasmey (thekingq20) wants to merge 1 commit into
microsoft:mainfrom
thekingq20:thekingq20-secureboot-fixes
Open

CHEA Oudomrasmey (thekingq20) wants to merge 1 commit into
microsoft:mainfrom
thekingq20:thekingq20-secureboot-fixes

Conversation

@thekingq20

@thekingq20 CHEA Oudomrasmey (thekingq20) commented Oct 4, 2026 •

Copy link
Copy Markdown

Description

PEM certificate files were not reliably recognized or decoded by the secure boot default key generator. This change extracts the base64 payload from PEM armor, validates decoding, accepts .pem and .cer extensions, and adds regression coverage. It also makes revocation-list selection skip filenames without numeric version suffixes instead of failing on them.

The workspace changes include line-ending normalization across multiple files, which accounts for much of the diff volume.

For details on how to complete these options and their meaning refer to CONTRIBUTING.md.

  • Impacts functionality?
  • Impacts security?
  • Breaking change?
  • Includes tests?
  • Includes documentation?

How This Was Tested

  • C:\Users\the20\AppData\Local\Programs\Python\Python312\python.exe -m pytest -q
  • Result: 19 passed

Integration Instructions

N/A

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@thekingq20

Copy link
Copy Markdown
Author

@microsoft-github-policy-service agree

@Flickdm

Copy link
Copy Markdown
Member

Thanks for looking at this! Can you rebase against main and ensure line endings are consistent and force push? There are a lot of changes that are not associated directly with your change.

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.

3 participants