Lines Matching refs:secure

309         int "eFuse secure version of app"
313             The secure version is the sequence number stored in the header of each firmware.
320             The app is booted with a higher (or equal) secure version.
328         int "Size of the efuse secure version field"
337             The size of the efuse secure version field.
342         bool "Emulate operations with efuse secure version(only test)"
348 …      This option allows to emulate read/write operations with all eFuses and efuse secure version.
357         # options, allowing to turn on "allow insecure options" and have secure boot with
503         # RSA secure boot is supported in ESP32 revision >= v3.0
540 …is option uses the same app signature scheme as hardware secure boot, but unlike hardware secure b…
553             There are two secure boot versions:
556                 - Legacy custom secure boot scheme. Supported in ESP32 SoC.
559                 - RSA based secure boot scheme.
562                 - ECDSA based secure boot scheme. Supported in ESP32-C2 SoC.
619 …          If hardware secure boot is enabled, this option is always enabled and cannot be disabled.
620 …If hardware secure boot is not enabled, this option doesn't add significant security by itself so …
633 …          If hardware secure boot is enabled, this option is always enabled and cannot be disabled.
634 …If hardware secure boot is not enabled, this option still adds significant security against networ…
648             updated apps once secure boot is enabled.
650 …     When enabling secure boot, JTAG and ROM BASIC Interpreter are permanently disabled by default.
653         bool "Select secure boot version"
658             Secure Boot V2 is the new RSA / ECDSA based secure boot scheme.
663 …Please note that, RSA or ECDSA secure boot is property of specific SoC based on its HW design, sup…
667             Secure Boot V1 is the AES based (custom) secure boot scheme supported in ESP32 SoC.
673                 Build a bootloader which enables secure boot version 1 on first boot.
702 … Generate a reusable secure bootloader key, derived (via SHA-256) from the secure boot signing key.
704 …This allows the secure bootloader to be re-flashed by anyone with access to the secure boot signing
707 …   This option is less secure than one-time flash, because a leak of the digest key from one device
717 …       Once secure boot or signed app requirement is enabled, app images are required to be signed.
765 …         Revocation of keys does not happen when enabling secure boot. Once secure boot is enabled,
780 …In reflashable secure bootloader mode, a hardware key is derived from the signing key (with SHA-25…
802 …You can disable some of the default protections offered by secure boot, in order to enable testing…
857 …to flash.) This mode is not secure, it's possible for an attacker to write their own chosen plaint…
901                 When either flash encryption or secure boot are enabled, the default is to
914                 when either secure boot or flash encryption is enabled.
917                 and some of the protections of secure boot.
1058             when secure boot is enabled.
1124                 It is also possible to enable secure download mode at runtime by calling