Searched refs:encrypted (Results 1 – 14 of 14) sorted by relevance
| /mcuboot-3.4.0/ext/tinycrypt/tests/ |
| D | test_cbc_mode.c | 108 uint8_t encrypted[80]; in test_1_and_2() local
119 if (tc_cbc_mode_encrypt(encrypted, sizeof(plaintext) + TC_AES_BLOCK_SIZE, in test_1_and_2()
127 result = check_result(1, ciphertext, sizeof(encrypted), encrypted, in test_1_and_2()
128 sizeof(encrypted)); in test_1_and_2()
134 p = &encrypted[TC_AES_BLOCK_SIZE]; in test_1_and_2()
135 length = ((unsigned int) sizeof(encrypted)) - TC_AES_BLOCK_SIZE; in test_1_and_2()
138 encrypted, &a) == 0) { in test_1_and_2()
|
| /mcuboot-3.4.0/boot/bootutil/ |
| D | CMakeLists.txt | 23 src/encrypted.c
|
| /mcuboot-3.4.0/boot/cypress/BlinkyApp/ |
| D | Readme.md | 102 **How to build encrypted upgrade image :**
104 To prepare MCUBootApp for work with encrypted upgrade image please refer to `MCUBootApp/Readme.md`.
106 To obtain encrypted upgrade image of BlinkyApp extra flag `ENC_IMG=1` should be passed in command l…
140 - `ENC_IMG` - 0 (default) - build regular upgrade image, `1` - build encrypted upgrade image (MCUBo…
|
| /mcuboot-3.4.0/boot/zephyr/ |
| D | Kconfig | 291 bool "Save encrypted key TLVs instead of plaintext keys in swap metadata"
294 If y, instead of saving the encrypted image keys in plaintext in the
295 swap resume metadata, save the encrypted image TLVs. This should be used
309 bool "Support for encrypted upgrade images using RSA"
312 If y, images in the secondary slot can be encrypted and are decrypted
313 on the fly when upgrading to the primary slot, as well as encrypted
318 bool "Support for encrypted upgrade images using ECIES-P256"
321 If y, images in the secondary slot can be encrypted and are decrypted
322 on the fly when upgrading to the primary slot, as well as encrypted
328 bool "Support for encrypted upgrade images using ECIES-X25519"
[all …]
|
| D | CMakeLists.txt | 101 ${BOOT_DIR}/bootutil/src/encrypted.c
184 ${BOOT_DIR}/bootutil/src/encrypted.c
|
| D | Kconfig.serial_recovery | 139 bool "Support for encrypted upgrade images using ECIES-P256 in serial recovery upload"
|
| /mcuboot-3.4.0/docs/ |
| D | SECURITY.md | 15 If you wish to send an encrypted email, you may use these PGP keys:
|
| D | release-notes.md | 98 entire contents of flash to always remain encrypted.
152 X25519 encrypted images, rollback protection, hardware keys, and a
163 - Add support for X25519 encrypted images.
189 The 1.5.0 release of MCUboot adds support for encrypted images using
270 In addition, support has been added for encrypted images. See [the
287 - Add support for [encrypted images](encrypted_images.md).
|
| D | readme-espressif.md | 160 [MCUboot encrypted images](encrypted_images.md) do not provide full code confidentiality when only …
321 …ough eFuse burning on the device, all read and write operations are decrypted/encrypted in runtime.
389 First ensure that the application image is able to perform encrypted read and write operations to t…
406 First ensure that the application image is able to perform encrypted read and write operations to t…
462 …ns are decrypted/encrypted in runtime, so as e.g. if pre-encrypted data is sent for an OTA update,…
464 For updating with an image encrypted on the host, flash it through serial using `esptool.py` as abo…
|
| D | imgtool.md | 89 --save-enctlv When upgrading, save encrypted key TLVs
|
| /mcuboot-3.4.0/boot/espressif/ |
| D | CMakeLists.txt | 135 ${BOOTUTIL_DIR}/src/encrypted.c
|
| /mcuboot-3.4.0/boot/cypress/MCUBootApp/ |
| D | README.md | 164 After MCUBootApp is built with these settings unencrypted and encrypted images will be accepted in …
|
| /mcuboot-3.4.0/sim/src/ |
| D | image.rs | 1904 let encrypted = Caps::EncRsa.present() || Caps::EncKw.present() || in find() localVariable
1906 match (encrypted, slot) { in find()
|
| /mcuboot-3.4.0/ext/tinycrypt/documentation/ |
| D | tinycrypt.rst | 233 same nonce for two different messages which are encrypted with the same
|
