Lines Matching refs:no
37 …:esp32: - ``--no-protect-key``. Disable default read and write protecting of the key. If this opti…
38 …:not esp32: - ``--no-write-protect``. Disable write-protecting of the key. The key remains writabl…
39 …:not esp32: - ``--no-read-protect``. Disable read-protecting of the key. The key remains readable …
60 …key purpose is burned as well with write protection (the ``--no-write-protect`` flag has no effect…
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.
118 Only flash encryption key is read protected if ``--no-read-protect`` is not used.
137 …The ``--no-protect-key`` option will disable this behaviour (you can separately read or write prot…
141 …The ``--no-read-protect`` and ``--no-write-protect`` options will disable this behaviour (you can …
208 When the ``no protection`` option is used then you can see the burned key:
212 > espefuse.py burn_key flash_encryption 256bit_fe_key.bin --no-protect-key
220 Key is left unprotected as per --no-protect-key argument.
222 The key block will left readable and writeable (due to --no-protect-key)
248 This example uses ``--no-read-protect`` to expose the byte order written into eFuse blocks.
259 …> espefuse.py burn_key BLOCK_KEY0 ~/esp/tests/efuse/512bits_0.bin XTS_AES_256_KEY --no-read-prote…
276 Keys will remain readable (due to --no-read-protect)