Skip to main content

ESP32S3: Flash Encryption and Secure Boot

Flash encryption and secure boot are useful security features for ESP32S3 chip. While not perfect, they definitely make it harder to extract the secrets in the chip.

However, it is tricky to enable both features at the same time. The topic is actually discussed in the official documentation:

Especially, the second one mentioned it is recommended to enable flash encryption before secure boot. But I still find the documentation confusing.

In the end I was able to successfully enable both, here's my findings.

My Understanding

After my adventure, here's what I think could have worked. WARNING, this is untested.

  • Follow Security Features Enablement Workflows:
    • Burn all the keys, as long as their purpose eFuses and read/write protections
    • Burn other security eFuses, but DO NOT burn ENABLE_SECURITY_DOWNLOAD in the middle, which is mentined at the end of the instruction for both flash encryption and secure boot.
    • Burn SPI_BOOT_CRYPT_CNT (all 3 bits) and SECURE_BOOT_EN
  • Sign bootloader and application
  • Encrypt signed bootloader, partition table and signed application
  • Flash three encrypted pieces into correct offsets.

My Actual Adventure

I had thought the official bootloader was necessary to enable the features, so I actually downloaded ESP-IDF and flashed the bootloader as the last step of enabling flash encryption. Later I found that ENABLE_SECURITY_DOWNLOAD had been automatically burned by the bootloader, because I used the recommended "secure download mode" option in `idf.py menuconfig`.

This is not the end of the world, it just meant I could no longer use `espefuse.py`. I could actually use the C API to burn the eFuses. The API is actually quite user-friendly, and the high-level functions (e.g. burn key, purpose and read/write protection at the same time) do check common errors. I just had to read the documentation to understand the differences between blocks, bits and registers.


One more thing about the bootloader: A recent version (5.3-ish) of ESP-IDF changed something about application image header, which is no longer compatible with esp-hal before this change, this took me quite a while to figure out.

Comments

Popular posts from this blog

Determine Perspective Lines With Off-page Vanishing Point

In perspective drawing, a vanishing point represents a group of parallel lines, in other words, a direction. For any point on the paper, if we want a line towards the same direction (in the 3d space), we simply draw a line through it and the vanishing point. But sometimes the vanishing point is too far away, such that it is outside the paper/canvas. In this example, we have a point P and two perspective lines L1 and L2. The vanishing point VP is naturally the intersection of L1 and L2. The task is to draw a line through P and VP, without having VP on the paper. I am aware of a few traditional solutions: 1. Use extra pieces of paper such that we can extend L1 and L2 until we see VP. 2. Draw everything in a smaller scale, such that we can see both P and VP on the paper. Draw the line and scale everything back. 3. Draw a perspective grid using the Brewer Method. #1 and #2 might be quite practical. #3 may not guarantee a solution, unless we can measure distances/p...

Installing Linux on Surface Pro 1g

Windows 10 will soon reach its end of life, and my 1-gen Surface Pro is not supported by Windows 11. I (finally) decided to install Linux to it. Fortunately, it's a not-so-easy nice adventure: The device has only one USB port, so I have to bring back my 10+-year old USB hub. My live USB drive cannot boot directly, I have to disable Secure Boot first, by holding Volume Up during boot. I think years ago I learned that booting on USB might not work through a USB hub, but fortunatelly it worked well with my setup. This is done by holding Volume Down during boot. Wifi adapter was detected in the live Linux environment, but not functional. And I don't have a USB-Ethernet adapter. Luckily, nowadays we have USB-tethering from Android phones, which works out-of-the-box. Originally I planned to following this guide to set up root on ZFS, however, the system froze when building the ZFS kernel module. Then I decided to just use EXT4, yet I still learned a lot from the guide about disk par...

Hardware Password Manager

[Updates 2025-01-20] The original blog post assumes that all passwords are stored in one password manager, and the password manager either unlocks everything or nothing (e.g. Keepass). After discussing with friends, I realized that if I use something like pass , and I use a hardware GPG token, I can actually store and sync all encrypted passwords to all devices, because I will only decrypt the passwords on demand, and the computer will not see the GPG private key. The compromise is that the computer will see the list of all password entries (e.g. accounts), as well as a few other issues . I've been using Keepass for many years. I don't use online password services because I cannot fully trust them. Besides, I may not always have Internet connection, which is why I also don't use a self-hosted service. Everything has been working fine, until I turn my paranoid knob to the max. Here's the thought experiment . The Imaginary Scenario Let's say I have 100 PCs for differe...