-
Notifications
You must be signed in to change notification settings - Fork 60
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
The index of attack traces in v2 trace set #18
Comments
Hi, Actually the key is random for all the index of the v2 dataset. During the attack step, a fixed key is simulated by modifying the input plaintext that is used to compute the rank function. Details about such simulation can be found in the article: https://eprint.iacr.org/2021/592.pdf (Section 4, equation (7)). Regards, |
Oh, it's my bad not noticing you also released a new paper. Thanks for your reply anyway. |
Regarding this I came across some doubts that
I have trying to understand that how during the attack step we will be recovering the key bytes as we have different key for each different trace , Thanking you. @rstrullu @keykeykeykeyk |
In v2 trace set, do you use the fixed key after index 500,000? Thank you
The text was updated successfully, but these errors were encountered: