Skip to content

[Secure Boot KEK Update] TOSHIBA PK-Signed KEK Update - #433

Open
YN-1048 wants to merge 3 commits into
microsoft:mainfrom
YN-1048:kek-update/TOSHIBA
Open

[Secure Boot KEK Update] TOSHIBA PK-Signed KEK Update#433
YN-1048 wants to merge 3 commits into
microsoft:mainfrom
YN-1048:kek-update/TOSHIBA

Conversation

@YN-1048

@YN-1048 YN-1048 commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

OEM Certificate Submission

OEM Name: [TOSHIBA Corporation]
Contact Email: [yuki.numata.d89@mail.toshiba]

Certificate Details

  • Platform Key Thumbprint: [e03ae95f7862f2e1f75b367ed1372e73e8d8cbfd]
  • Expiration Date: [2028-10-27]

Testing Completed

  • [*] Windows validation
  • Linux validation

Security Review

  • [*] No known security issues

Additional Notes

None

@Flickdm Doug Flick (Flickdm) left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm going to follow back up with a update to the kek_update_map in a different PR

@Flickdm

Copy link
Copy Markdown
Member

FYI I'm going to fix up the kek update map once these are in as separate commit and remove the instructions to update it.

@Flickdm
Doug Flick (Flickdm) enabled auto-merge (rebase) July 1, 2026 22:47
auto-merge was automatically disabled July 1, 2026 22:52

Rebase failed

@SochiOgbuanya
SochiOgbuanya enabled auto-merge (squash) July 21, 2026 18:06
@YN-1048

YN-1048 commented Aug 18, 2026

Copy link
Copy Markdown
Contributor Author

Is there any additional work required on our part to have this reviewed?

@YN-1048

YN-1048 commented Aug 25, 2026

Copy link
Copy Markdown
Contributor Author

When will this matter be addressed?????

@Flickdm

Copy link
Copy Markdown
Member

When will this matter be addressed?????

Your PR has merge conflicts and merging is disabled unless you correct it - sadly I don't have permissions to address it for you - normally this would be resolved with a rebase. What I can do to make this move forward is to simply take your assets and make a PR myself as then I can address it.

@SochiOgbuanya

Copy link
Copy Markdown
Collaborator

Hello YN-1048, apologies for the delayed response. I was out of office for the past 2 weeks. You're PK signed KEK was included in the July Windows update B release - 07/14/2026. I do not have permissions to merge your PR into the main branch

Thanks,
Sochi

@Flickdm

Copy link
Copy Markdown
Member

Either we can close out this PR - and mine will be merged or you can take my fix.

#458

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.

4 participants