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

[Case Study 3] Verify replaced AES key #1

Open
e7p opened this issue Jan 8, 2024 · 0 comments
Open

[Case Study 3] Verify replaced AES key #1

e7p opened this issue Jan 8, 2024 · 0 comments
Assignees

Comments

@e7p
Copy link
Contributor

e7p commented Jan 8, 2024

According to Appendix A in the paper, we introduce the key 00 11 22 33 44 55 66 77 88 99 AA BB CC DD EE FF for every case study, as the AES test vectors are specified. However, I recall that the Verilog implementation of "instructionreplacementtrojan.sv" we used a different key for test purposes, namely F0 E0 D0 C0 B0 A0 90 80 70 60 50 40 30 20 10 00 that is more different to the original key and thus well-suited as a proof of concept. It should though not be a big deal to replace the trojan-key to the other one and test that the implementation still works as expected, it should result in the test vectors given in A.3.

@e7p e7p self-assigned this Jan 8, 2024
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

No branches or pull requests

1 participant