[spm] Introduce UDS/EXT aliases for certificate key labels #236
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.
This change introduces shorter, more stable aliases for certificate key labels used in the provisioning process. The aliases "UDS" (Unique Device Secret) and "EXT" (Extension) are now used by client applications.
The SPM service is responsible for mapping these aliases to the underlying key labels ("SigningKey/Dice/v0" and "SigningKey/Ext/v0"). This provides a layer of abstraction, making the client-side implementation cleaner and less coupled to the internal naming scheme.
Key changes:
spm
: Translates "UDS" and "EXT" labels to their full counterparts during key retrieval and certificate endorsement. It now gracefully handles missing certificates by returning an empty subject key.ate
: The client library now accepts the key label directly from the caller instead of hardcoding a mapping.pa/loadtest
,ate/test_programs/ft
: Updated to use the new "UDS" and "EXT" aliases.