ot-sca icon indicating copy to clipboard operation
ot-sca copied to clipboard

Side-channel analysis setup for OpenTitan

Results 35 ot-sca issues
Sort by recently updated
recently updated
newest added

As discussed with @vrozic , currently there is no CI job for testing the container. To ensure that future changes to the container infrastructure are working, adding a new CI...

Priority:P1

Similar to AES, we need to specify how we generate crypto material for KMAC batch mode.

Priority:P1

We currently use Python `random` host-side and an implementation of the same Mersenne twister on device side. - There is a danger of the Python class changing. - This is...

Priority:P1

Implement a mechanism to upload and download bitstreams and traces to/from gcp buckets. Additional requirements: * Store metadata associated with bitstream to be able to reproduce the build. For example,...

Priority:P2

PR #82 added the corresponding target binaries to support the aes-fvsr-key-batch command. For most of us this seems to work just fine but I saw lots of errors like: ```...

Priority:P2

As discussed in https://github.com/lowRISC/ot-sca/pull/115 and https://docs.google.com/document/d/1sZjASiUji_IT-t9jEFlK-kGc_Gw3mGfubNvpkM_IQT4/edit#heading=h.qd65x0y76b0e we should check the usage of `key, text = ktp.next()` in `cw/capture.py` Default behavior is that `ktp.next()` returns `const_key, random_plaintext`. This default behavior can...

good first issue
Priority:P2

Test capture script #150 uncovered a problem with naming of some of the capture commands and arguments. At the moment we don't use consistent naming strategy, which makes it complicated...

Priority:P2

When capturing traces on a CW310 / Husky setup we get traces on two different levels seemingly at random. Tested using: `./capture.py --cfg-file capture_aes_cw310.yaml capture aes-random --num-traces 100 --plot-traces 100`....

bug
Priority:P2

This PR adds experimental CW340 support with a minimal running capture script.

Currently, we're sampling with 50 MHz and the target is running at ~5 MHz for ECDSA captures to keep a 10x oversampling ratio (some of this work is not yet...