Repository navigation
fix(attestation): allow larger NVIDIA signing key sets - #1414
Merged
Merged
Conversation
henrypark133
approved these changes
Nov 14, 2026
Review · Status⬛ StoppedIronLoop stopped because the pull request was closed while this Run was active. Run detailsAutomatic trigger · attempt 1 of 3 · stopped after 3m 49s |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
NVIDIA's public signing key set can exceed the 64 KiB download limit because it includes certificate chains for retained keys. When the download exceeds that limit, GPU attestation fails before signature verification can start.
Raise the signing key set limit to 1 MiB. Signature, issuer, time, nonce, and per-GPU digest checks continue to apply. The regression test serves a large key set over HTTP and verifies a signed GPU attestation with it.
Validation