Description
Myster Mask has written an implementation that sucks big time!
You will have to analyze the consumption traces of the beginning of an implementation of the AES made by Myster Mask. Will you be able to exploit these traces to make the difference?
The part to be targeted corresponds to the inversion step present in the calculation of the S-box in the first round of the AES. Only this step is implemented, it is not necessary to know the details of the AES since this challenge is specifically focused on this inversion step.
The consumption traces provided in the traces.npz file to be loaded with numpy correspond to the following line in the myster_mask.py code:
``py
masked_inversion(L)
Beware, as a good detective, Myster Mask has protected this inversion by honoring his name.
Now it's your turn to play!
Files
-
output.txt
211 B – b5b68e6386b9d330d876214debbac881ee10f9b627936576d69b72266a93d2ad -
myster_mask.py
1.81 KiB – a9b3d567ab8c5344952303a2955a72157d1b7f302b94d9f71e24797c7bd6c28f -
inputs.npz
78.39 KiB – 283b4245a36d7d238ba941a247eaaa38cc90d8db2f3c4e7db824d241a6c21603 -
traces.npz
33.28 MiB – d4e16ded8c53f6e295672567cd8bdd3453ebd1318bf353b827c40cda17698fe4
Authors
Flag
Submit your solution
You can submit your writeup for this challenge. Read the FAQ to learn how to proceed.
You need to be logged in to submit a writeup.