-
Notifications
You must be signed in to change notification settings - Fork 30
Otsca test #398
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
base: master
Are you sure you want to change the base?
Otsca test #398
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Siemen for working this, having a test framework for ot-sca <-> pentest framework does have a huge impact on the maintainability of the pentesting infrastructure :)
I've dropped a couple of comments. It seems that your changes broke the current SCA capture scripts (please see the CI). In order to merge this we would need to make sure that they still work.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Siemen. I'd suggest a couple of points before we can merge this:
- Can you please rebase the PR such that we see that CI passes?
- Would it be possible to add a very brief documentation to
test/penetrationtests
, i.e., a brief how to run this? - Could you please squash some of the commits? E.g., creating a new communication folder and then moving it again at the end?
- Would it be possible to move the default configs for the target/communication scripts outside of these functions?
c36a40b
to
e8b1d8b
Compare
660cb46
to
31cf280
Compare
8aae6a2
to
eb0c143
Compare
ecbad43
to
9a9bbc4
Compare
0f1d2c7
to
2618750
Compare
23c4ffe
to
901171d
Compare
target/cw_fpga.py
Outdated
# Initialize ChipWhisperer scope. This is needed to program the binary. | ||
# Note that the actual scope config for capturing traces is later | ||
# initialized. | ||
self.scope = cw.scope(sn=self.husky_serial) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to keep passing the husky_serial
as somehow the CW driver needs that. Now, when having attached multiple CW Huskies, the CW driver asserts that multiple are attached and it needs the serial number.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will add it by updating your commit.
Bitstreams were generated with: ./bazelisk.sh build //hw/bitstream/vivado:fpga_cw310_test_rom ot-sca_cw310 binaries & bitstreams & opentitantool: commit: lowRISC/opentitan@867c06a ot-sca_cw310_aes binaries & bitstreams: commit: lowRISC/opentitan@51a8f50 ot-sca_cw310_otbn binaries & bitstreams: commit: lowRISC/opentitan@2898576 ot-sca_cw310_kmac binaries & bitstreams: commit: lowRISC/opentitan@a288f62 Signed-off-by: Pascal Nasahl <[email protected]>
Update the yaml files to version v1.0.3 of OpenTitan's pentest framework. Signed-off-by: Siemen Dhooghe <[email protected]>
Integrate the capture and fault injection scripts to the latest pentest framework v1.0.3. This also deprecates the CW305 board and removes the output_len and input_len values in the cfg. Signed-off-by: Siemen Dhooghe <[email protected]> Co-authored-by: Pascal Nasahl <[email protected]>
Update ot-sca to latest pentestOS on OT.
To do: