Lines Matching full:with
12 - distributed with this work for additional information
16 - with the License. You may obtain a copy of the License at
46 The bootloader currently only supports images with the following
114 #define IMAGE_TLV_ENC_RSA2048 0x30 /* Key encrypted with RSA-OAEP-2048 */
115 #define IMAGE_TLV_ENC_KW 0x31 /* Key encrypted with AES-KW-128 or
117 #define IMAGE_TLV_ENC_EC256 0x32 /* Key encrypted with ECIES-P256 */
118 #define IMAGE_TLV_ENC_X25519 0x33 /* Key encrypted with ECIES-X25519 */
127 If protected TLVs are present then a TLV info header with magic equal to
141 region of disk with the following properties:
152 /* If the bootloader is working with the first image */
157 /* If the bootloader is working with the second image */
210 Let's assume, for example, a device with 10000 erase cycles, an image size of
292 image headers. It selects the newest image (with the highest version number) and
348 When the encryption option is enabled (`MCUBOOT_ENC_IMAGES`) along with ram-load
362 Upgrading an old image with a new one by swapping can be a two-step process. In
413 enabled with the MCUBOOT_DIRECT_XIP_REVERT config option and an image trailer
528 to be swapped (based on the slot with largest image + TLVs) is written to
604 could be huge. For example, for 128 slot sectors with a 4-byte alignment,
700 *signing error. This state behaves as State IV with the extra action of*
716 With the terms defined, we can now explore the bootloader's operation. First,
745 is a bit more complex but similar to the previously described procedure with
850 + No: Return with failure.
894 with the greatest index); only regions that are predetermined to be part of
923 trailer can be written by the user at a later time. With the image trailer
1008 Finally, reverse the list of indices such that the list starts with index
1009 `BOOT_MAX_IMG_SECTORS - 1` and ends with 0. The swap status region is a
1045 device's image slots have been configured with `BOOT_MAX_IMG_SECTORS: 128` and
1144 with magic equal to `IMAGE_TLV_INFO_MAGIC` must be present.
1148 KEYHASH TLV with the hash of the key that was used to sign. The list of
1159 running validation again. Enabling this option should be done with care.
1166 image was signed with a private key that corresponds to the embedded KEYHASH
1204 TLV area and compares it with the key-hash that was retrieved from the device.
1205 - `MCUBOOT_BUILTIN_KEY`: With this option the whole public key(s) used for
1213 ***Note:*** *At the moment the usage of builtin keys is only available with the*
1219 If the TLV area contains protected TLV entries, by beginning with a `struct
1220 image_tlv_info` with a magic value of `IMAGE_TLV_PROT_INFO_MAGIC` then the
1223 the size of the protected TLVs together with the size of the `image_tlv_info`
1238 | +-----------------+ | struct image_tlv_info with
1243 | | TLV area header | | <- struct image_tlv_info with IMAGE_TLV_INFO_MAGIC
1261 The dependencies between images can be described with additional TLV entries in
1288 compared. This feature is enabled with the `MCUBOOT_DOWNGRADE_PREVENTION`
1298 new image's security counter will be compared with the currently active security
1303 * It does not need to increase with each software release,
1307 It is an optional step of the image validation process and can be enabled with
1316 with the runtime software. If any of these are enabled the target must provide
1327 with zeros and a TLV header is added at the beginning of the area during an
1328 initialization phase. This TLV header contains a `tlv_magic` field with a value
1354 The measured boot can be enabled with the `MCUBOOT_MEASURED_BOOT` config option.
1386 in `boot/bootutil/include/bootutil/boot_status.h` with `BLINFO_` prefixes.
1409 sense in the simulator environment running on a host machine with different
1412 with `-O0` optimisation is more resilient against FI attacks than the code
1413 generated with `-O3` or `-Os` optimizations.
1435 # Calling the function with different parameters is done by Travis CI based on
1480 executed successfully. A yaml file is created during test execution with the
1505 - The docker image needs to be built with `ci/fih-tests_install.sh` as described
1507 - Start the docker image with the following command:
1509 - Execute the test with a command similar to the following:
1512 possible to stop the test with _Ctrl+c_. The parameters to the