docs/en/security: Add documentation for signed apps without hardware secure boot feature
This commit is contained in:
committed by
Angus Gratton
parent
b069b31a2c
commit
7d847e60ec
@@ -29,6 +29,11 @@ Application Example
|
||||
return ESP_OK;
|
||||
}
|
||||
|
||||
Signature Verification
|
||||
----------------------
|
||||
|
||||
For additional security, signature of OTA firmware images can be verified. For that, refer :ref:`secure-ota-updates`
|
||||
|
||||
API Reference
|
||||
-------------
|
||||
|
||||
|
||||
@@ -32,6 +32,13 @@ The OTA data partition is two flash sectors (0x2000 bytes) in size, to prevent p
|
||||
while it is being written. Sectors are independently erased and written with matching data, and if they disagree a
|
||||
counter field is used to determine which sector was written more recently.
|
||||
|
||||
.. _secure-ota-updates:
|
||||
|
||||
Secure OTA Updates Without Secure boot
|
||||
--------------------------------------
|
||||
|
||||
The verification of signed OTA updates can be performed even without enabling hardware secure boot. For doing so, refer :ref:`signed-app-verify`
|
||||
|
||||
See also
|
||||
--------
|
||||
|
||||
|
||||
Reference in New Issue
Block a user