ot-sca
ot-sca copied to clipboard
lowRISC
Side-channel analysis setup for OpenTitan
When using the new OT trace database in a multi-processing setting (e.g., CECA.py), the new DB is slower than the older CW DB. The reason for that is how the...
Currently, CI only runs a basic AES test for TVLA. We should extend CI to also test other features. However, as I am not aware of which features are actually...
The CW305 has a couple of advantages over the CW310/CW340 when it comes to debugging/optimizing countermeasures. However, it currently cannot be used for uJSON captures. ~What needs to be done...
When doing FPGA measurements, I noticed that - at least for AES - we no longer have range / saturation checks for Husky. If the user chooses a gain value...
Currently, a small timeout ([`time.sleep(0.01)`](https://github.com/lowRISC/ot-sca/blob/e20ffa3f0210cf8b568d6bae89f59e1b6587bcf3/capture/lib/ot_communication.py#L43)) between uJSON commands are needed to prevent that the receive buffers overflow and the message gets lost. To speed up capture rate, we should get...
Currently, the sampling rate needs to be set in the config file by the user although the sampling rate is fetched directly from the WaveRunner scope. To overcome this issue,...
Currently, the KMAC script uses variable names from AES (ciphertext instead of mac/tag). We should change this in the script as well as in the trace database to maintain readability.
When the simple capture script is mature enough, use as template to implement remaining capture commands.
With the PR https://github.com/lowRISC/ot-sca/pull/95, we can now load histograms and use them for general test. This is done automatically when a PR is created but it does not cover all...
