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

The index of attack traces in v2 trace set #18

Closed
keykeykeykeyk opened this issue Jun 4, 2021 · 3 comments
Closed

The index of attack traces in v2 trace set #18

keykeykeykeyk opened this issue Jun 4, 2021 · 3 comments

Comments

@keykeykeykeyk
Copy link

In v2 trace set, do you use the fixed key after index 500,000? Thank you

@rstrullu
Copy link

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,
ASCAD Team

@keykeykeykeyk
Copy link
Author

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,
ASCAD Team

Oh, it's my bad not noticing you also released a new paper. Thanks for your reply anyway.

@Vaibhav-Sharma010204
Copy link

Regarding this I came across some doubts that

  1. In v2 dataset we have different random keys for each pair of plain text , masks and trace so Please clear us that is there any way that all the different keys which have been given produces us the same master key through masking of given different key bytes in Metadata
    or it's vice versa that given key has been already masked and provided to us in the dataset then how we can derive a common key through them

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

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

4 participants