Skip to content

Conversation

@Faintsnow
Copy link

OEM Certificate Submission
OEM Name: TONGFANG
Contact Email: faintsnow.bu@aistoneglobal.com

Certificate Details
Platform Key Thumbprint: 31c22f2a60bc83a1e361ee6959b5cdd7f4940a5e
Expiration Date: 2044-08-22

Testing Completed
Windows validation
Linux validation
Security Review
No known security issues
Additional Notes
None

@Faintsnow
Copy link
Author

@microsoft-github-policy-service agree company="TONGFANG"

@Faintsnow
Copy link
Author

Faintsnow commented Nov 24, 2025 via email

@Flickdm Flickdm merged commit 57209ae into microsoft:main Nov 25, 2025
2 checks passed
@hughsie
Copy link

hughsie commented Nov 26, 2025

Are we sure about this one?

fwupdtool firmware-parse ../secureboot_objects/PostSignedObjects/KEK/TONGFANG/KEKUpdate_TONGFANG_PK31C22F2A.bin efi-variable-authentication2 --json
{
  "Error" : {
    "Domain" : "FwupdError",
    "Code" : 18,
    "Message" : "SignatureListSize invalid: 0x0"
  }
}

there looks to be some extra content:

09:18:06.407 FuStruct             FuStructEfiVariableAuthentication2:
  timestamp: FuStructEfiTime:
  year: 0x7da
  month: 0x3
  day: 0x6
  hour: 0x13
  minute: 0x11
  second: 0x15
  nanosecond: 0x0
  timezone: 0x0
  daylight: 0x0
  auth_info: FuStructEfiWinCertificate:
  length: 0x4e8
09:18:06.408 FuStruct             FuStructEfiSignatureList:
  type: a5c059a1-94e4-4aa7-87b5-ab155c2bf072
  list_size: 0x5e2
  header_size: 0x0
  size: 0x5c6
09:18:06.408 FuStruct             FuStructEfiSignatureList:
  type: 00000000-0000-0000-0000-000000000000
  list_size: 0x0
  header_size: 0x0
  size: 0x0

It could very well be a bug in my parser, but it's the first file that's shown this kind of issue.

@Flickdm
Copy link
Member

Flickdm commented Nov 27, 2025

I agree with @hughsie that this payload is invalid. @Faintsnow can you explain what the payload was? The only valid payload that will be accepted is an EFI_SIGNATURE_LIST of type x509 containing strictly the 2023 Microsoft KeK authority.

I have reverted that payload until both a valid answer and updated payload are provided and halted accepting until CI gates are put in place.

For reference for servicing, we do not use the provided payload and assume that all OEMs use the exact payloads we asked them to provide. Anything else will fail.

Faintsnow pushed a commit to Faintsnow/secureboot_objects that referenced this pull request Nov 27, 2025
@Faintsnow
Copy link
Author

Faintsnow commented Nov 27, 2025

I apologize, I uploaded the wrong KEKUpdate binary(it was merged with the orginal KEK_SigListContent.bin).
I have fixed and resubmitted the correct one.@Flickdm

Faintsnow pushed a commit to Faintsnow/secureboot_objects that referenced this pull request Nov 27, 2025
Faintsnow pushed a commit to Faintsnow/secureboot_objects that referenced this pull request Nov 27, 2025
@Flickdm
Copy link
Member

Flickdm commented Nov 27, 2025

@Faintsnow Thank you for the update! I can confirm that the payload looks correct. I'll re-add your submission once people get back from the holidays - Thanks!

@Faintsnow
Copy link
Author

Hi @Flickdm, it seems like it's been quite a while since your last reply, but haven't re-add my submission.
Just wanted to remind you in case you forget.
Thanks.

@Flickdm
Copy link
Member

Flickdm commented Dec 15, 2025

Hi @Flickdm, it seems like it's been quite a while since your last reply, but haven't re-add my submission. Just wanted to remind you in case you forget. Thanks.

Thanks for the reminder! It doesn't look like github allows me to reopen this submission, are you able to create a new PR?

Faintsnow pushed a commit to Faintsnow/secureboot_objects that referenced this pull request Dec 16, 2025
@Faintsnow
Copy link
Author

Hi @Flickdm, I have created a new PR.
#335
Thanks.

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