From 2a4fddb48b9ab5d2ae45f700eb828bface7554eb Mon Sep 17 00:00:00 2001 From: Aditya Patwardhan Date: Thu, 22 Jun 2023 17:18:08 +0530 Subject: [PATCH] docs/Security:Add references to second stage bootloader to avoid confusion bettwen bootloader and 2nd stage bootloader --- docs/en/security/flash-encryption.rst | 2 +- docs/en/security/host-based-security-workflows.rst | 2 +- docs/en/security/secure-boot-v2.rst | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/en/security/flash-encryption.rst b/docs/en/security/flash-encryption.rst index cb4e5aafd7..12c330054d 100644 --- a/docs/en/security/flash-encryption.rst +++ b/docs/en/security/flash-encryption.rst @@ -36,7 +36,7 @@ Encrypted Partitions With flash encryption enabled, the following types of data are encrypted by default: -- Firmware bootloader +- :ref:`second-stage-bootloader` (Firmware Bootloader) - Partition Table - :ref:`nvs_encr_key_partition` - Otadata diff --git a/docs/en/security/host-based-security-workflows.rst b/docs/en/security/host-based-security-workflows.rst index eee69163a5..f74be6ba02 100644 --- a/docs/en/security/host-based-security-workflows.rst +++ b/docs/en/security/host-based-security-workflows.rst @@ -18,7 +18,7 @@ Goals #. Simplify the traditional workflow with stepwise instructions. #. Design a more flexible workflow as compared to the traditional firmware based workflow. #. Improve reliability by dividing the workflow in small operations. -#. Eliminate dependency on firmware bootloader. +#. Eliminate dependency on :ref:`second-stage-bootloader` (firmware bootloader). Pre-requisite ------------- diff --git a/docs/en/security/secure-boot-v2.rst b/docs/en/security/secure-boot-v2.rst index b81383e6cf..b06fbe70ca 100644 --- a/docs/en/security/secure-boot-v2.rst +++ b/docs/en/security/secure-boot-v2.rst @@ -27,7 +27,7 @@ Secure Boot V2 For ESP32 before ECO3, refer to :doc:`Secure Boot `. It is recommended that users use Secure Boot V2 if they have a chip version that supports it. Secure Boot V2 is safer and more flexible than Secure Boot V1. - Secure Boot V2 uses {IDF_TARGET_SBV2_SCHEME} based app and bootloader verification. This document can also be used as a reference for signing apps using the {IDF_TARGET_SBV2_SCHEME} scheme without signing the bootloader. + Secure Boot V2 uses {IDF_TARGET_SBV2_SCHEME} based app and bootloader (:ref:`second-stage-bootloader`) verification. This document can also be used as a reference for signing apps using the {IDF_TARGET_SBV2_SCHEME} scheme without signing the bootloader. .. only:: esp32