Skip to content

Commit fa6520d

Browse files
Update UseSecurityFeatures.md
1 parent 8eb07ea commit fa6520d

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

UseSecurityFeatures.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,8 @@ In the [Getting Started Guide](GettingStartedGuide.md), one would have setup the
2020
9. Go back to `Security features`.
2121
10. Go back to main menu, Save and Exit.
2222

23+
**NOTE**: For production devices refer to Espressif's documentation on [**Release Mode** for Flash Encryption](https://docs.espressif.com/projects/esp-idf/en/latest/esp32c3/security/flash-encryption.html#release-mode)
24+
2325
## 4 Provision the ESP32-C3 with the private key, device certificate and CA certificate in Development Mode
2426
The key and certificates which will be used to establish a secure TLS connection will be encrypted and stored in a special flash partition.
2527

@@ -57,6 +59,8 @@ Note: If you have installed openssl and the openssl command fails with a command
5759
6. Set `Secure boot private signing key` to the path to the RSA 3072 private key you generated in step 1.
5860
7. Go back to main menu, Save and Exit.
5961

62+
**NOTE**: This covers setting up Secure Boot with a single private key, but up to 3 private keys can be used. Refer to Espressif's documentation on [Secure Boot V2](https://docs.espressif.com/projects/esp-idf/en/latest/esp32c3/security/secure-boot-v2.html)
63+
6064
### 5.1 Build and flash the Secure Boot enabled bootloader
6165
1. Build the bootloader by running the following command:
6266
```
@@ -88,6 +92,8 @@ idf.py -p PORT flash monitor
8892
```
8993
Replace **PORT** with the serial port to which the ESP32-C3 is connected.
9094

95+
**NOTE**: If Flash Encryption was enabled, instead of `flash`, you must use `encrypted-flash` to flash the board after this step. If flashing to an encrypted part of flash with `esptool.py`, you must also add the `--encrypt` option.
96+
9197
## 7 Monitoring the demo
9298

9399
1. On the serial terminal console, confirm that the TLS connection was successful and that MQTT messages are published.

0 commit comments

Comments
 (0)