Implement key ladder in ROM and RT FW. #1874
Open
Conversation
This file contains 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
The key ladder is initialized in cold-boot from LDevID CDI. It is lengthened during update-reset flows to match min-SVN-since-cold-boot. This PR does not include a smoke test, because the production application firmware doesn't yet include any APIs for exercising the key ladder. The additional cycles from this feature depends on the firmware's SVN, and is roughly 2.7k cycles * (128 - fw_svn). In the worst case, when fw_svn = 0, the cycle count is ~350k.
bluegate010
requested review from
jhand2,
fdamato,
rusty1968,
mhatrevi,
swenson,
vsonims,
FerralCoder,
ajisaxena,
korran and
JohnTraverAmd
as code owners
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.
The key ladder is initialized in cold-boot from LDevID CDI. It is lengthened during update-reset flows to match min-SVN-since-cold-boot.
This PR does not include a smoke test, because the production application firmware doesn't yet include any APIs for exercising the key ladder.
The additional cycles from this feature depends on the firmware's SVN, and is roughly 2.7k cycles * (128 - fw_svn). In the worst case, when fw_svn = 0, the cycle count is ~350k.