Reuse PrgFixedKeyAes128 keys within IDPF calls #525
Merged
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.
Stacked on top of #523.
This adds a new path to construct
PrgFixedKeyAes128
, reusing cSHAKE128 computations across many PRG instances. The IDPF generate and evaluate functions are then modified to use this new API, and pass the fixed key around instead of the binder. This leads to some tremendous speedups, as we are now fully exploiting the lower cost of PrgFixedKeyAes128.Closes #511.