You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Add notes about MbedTLS and hardened stages to readme
* Modify enc_bootloader example to use latest mbedtls code from picotool
Also, fix stdio_uart and stdio_usb output when running clk_sys from rosc, and fix having stdio_usb in both the bootloader and the binary
* Mention mbedtls insecurity in enc_bootloader readme
Copy file name to clipboardExpand all lines: README.md
+2-1Lines changed: 2 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -90,7 +90,8 @@ App|Description
90
90
91
91
App|Description
92
92
---|---
93
-
[hello_encrypted](encrypted/hello_encrypted) | Create a self-decrypting binary.
93
+
[hello_encrypted](encrypted/hello_encrypted) | Create a self-decrypting binary, using the hardened decryption stage. This should be secure against side channel attacks.
94
+
[hello_encrypted_mbedtls](encrypted/hello_encrypted) | Create a self-decrypting binary, using the MbedTLS decryption stage. This is not secure against side channel attacks, so is fast but provides limited protection.
Copy file name to clipboardExpand all lines: bootloaders/encrypted/README.md
+2Lines changed: 2 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,7 @@
1
1
For security you **must** replace private.pem and privateaes.bin with your own keys, and ivsalt.bin with your own per-device salt. Make sure you **don't lose your keys and salts**, else you may not be able to update the code on your device.
2
2
3
+
This bootloader uses MbedTLS for decryption, so it is not secure against side channel attacks and therefore only offers limited protection against physical attackers.
4
+
3
5
Your signing key must be for the _secp256k1_ curve, in PEM format. You can create a .PEM file with:
0 commit comments