Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[aes] Fix aes_fvsr_key_batch on CW305 #137

Merged
merged 1 commit into from
Apr 17, 2023

Conversation

vogelpi
Copy link
Collaborator

@vogelpi vogelpi commented Apr 14, 2023

Previously, the commands for seeding the batch PRNG and seeting the fixed key seemed to interfere resulting in the target implemented on the CW305 getting completely out of sync.

Previously, the commands for seeding the batch PRNG and seeting the
fixed key seemed to interfere resulting in the target implemented on
the CW305 getting completely out of sync.

Signed-off-by: Pirmin Vogel <[email protected]>
Copy link

@abdullahvarici abdullahvarici left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks Pirmin but we can think this as a temporary and quick fix. But at the end we should implement Colin's suggestion but it also needs some modification on OTBN binary side.

@vogelpi
Copy link
Collaborator Author

vogelpi commented Apr 17, 2023

LGTM. Thanks Pirmin but we can think this as a temporary and quick fix. But at the end we should implement Colin's suggestion but it also needs some modification on OTBN binary side.

Thanks for your review @abdullahvarici ! Ah, that's were this issue is :-) I vaguely remembered something but forgot to check. I agree that we should investigate this and come up with a real/more reliable fix.

@vogelpi vogelpi merged commit 6b41a34 into lowRISC:master Apr 17, 2023
@vogelpi vogelpi deleted the fix-aes-fvsr-key-batch-cw305 branch April 17, 2023 16:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants