Lines Matching refs:keys
6 The ``espefuse.py burn_key`` command burns keys to eFuse blocks:
38 …ect``. Disable write-protecting of the key. The key remains writable. The keys use the RS coding s…
45 {IDF_TARGET_NAME} supports keys:
50 … and write protected. The hardware will still have access to them. These keys are burned in rever…
56 …mes ``BLOCK1`` and ``BLOCK2`` to burn flash encryption and secure boot v2 keys because byte order …
68 …:esp32h2: - ECDSA_KEY. It can be ECDSA private keys based on NIST192p or NIST256p curve. The priva…
81 …es and supports private keys based on the NIST192p or NIST256p curve. These two commands below can…
97 … secure boot keys. This chip does not have any eFuse key purpose fields, but we use the key purpos…
106 {IDF_TARGET_NAME} can have in eFuse block the following combination of keys:
112 5. no keys, used for user purposes. Chip does not have security features.
116 All keys will be burned with write protection if ``--no-write-protect`` is not used.
120 …All keys, except flash encryption, will be burned in direct byte order. The encryption key is writ…
127 …scheme is in use, keys are 256-bits (32 bytes) long. When 3/4 Coding Scheme is in use (``CODING_SC…
173 Burn keys to blocks:
179 Burn keys in efuse blocks.
216 Burn keys to blocks:
221 Burn keys in efuse blocks.
263 Burn keys to blocks:
317 Burn keys to blocks:
326 Burn keys to blocks: