This repository has been archived by the owner on Dec 13, 2022. It is now read-only.
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.
Here's a sketch for an end-to-end theorem about a simple SHA256 program that reads a message from the byte array at
input_addr
, computes its digest using the bedrock2 driver and Cava Hmac module, and stores the digest into the byte array atdigest_addr
.It still contains some admits/TODOs related to bitfiddling and initial states, as well as a bigger TODO indicating that the Cava SHA256 module needs to be integrated as soon as it's ready, but the general structure is there.
For the moment, I made a new directory
silveroak-opentitan/Sha256End2End/
, and did not yet put it on CI, because it depends oninvestigations/cava2/
, which is not on CI either, and it requires that the directoriessilveroak-opentitan/hmac/Spec/
andfirmware/Hmac
are built before this one, but we have not yet discussed how to reflect this dependency on CI.