| /mcuboot-3.6.0/docs/ |
| D | ecdsa.md | 7 TLS) are fairly strict about the formatting of the ECDSA signature.
9 There are two ways to fix this:
21 generated. These tools are usually written in higher-level
34 Without this argument, the images are padded with the
66 ECDSA signatures are encoded as ASN.1, notably with the signature
76 Both `r` and `s` are 256-bit numbers. Because these are
77 unsigned numbers that are being encoded in ASN.1 as signed values, if
89 The correct approach here is to accept that ECDSA signatures are of
|
| D | encrypted_images.md | 33 decrypted (after validation). If swap upgrades are enabled, the image
55 TLVs are still sent as plain data.
69 `newt`. This key should never be reused and no checks are done for this,
81 are the results of applying the given operations over the AES-CTR key.
85 ECIES follows a well defined protocol to generate an encryption key. There are
86 multiple standards which differ only on which building blocks are used; for
87 MCUboot we settled on some primitives that are easily found on our crypto
96 are not using a `salt` and using an `info` of `MCUBoot_ECIES_v1`, generating
118 the TLV containing the key. Given that no errors are found, it will then
131 presence of the `ENCRYPTED` flag and the key TLV. If those are present the
[all …]
|
| D | readme-zephyr.md | 5 There are some pretty significant differences in how apps are built
6 for Zephyr, and these are documented here.
13 partitions defined in its device tree. These partitions are:
26 Currently, the two image slots must be contiguous. If you are running
28 so your SoC runs it out of reset. If there are multiple updateable images
33 The flash partitions are typically defined in the Zephyr boards folder, in a
53 the `CMakeLists.txt` file in boot/zephyr. There are comments there for
131 The signing keys used by MCUboot are represented in standard formats,
174 4KB, 8KB, 12KB, 16KB are allowed, 7KB, 7.5KB are not. This scratch partition
|
| D | PORTING.md | 16 OS must already have it bundled. The supported libraries at the moment are
64 Kconfig; these configuration systems are converted to MCUBOOT_ options
73 for MCUboot and images of applications are stored, in system-agnostic way.
76 Such flash regions are served by object of `const struct flash_area` type while
81 This way systems are free to implement internal logic of flash map or define
118 specific header files and are used to identify destination of flash area by ID:
136 The numbers, given above, are provided as an example and depend on system
184 To configure the what functions are called when allocating/deallocating
|
| D | release-notes.md | 59 are no longer in the code, a pem file must be supplied to extract
89 - Upgrade fault-injection hardening, improving cases injections are detected.
96 There are no security vulnerabilities reported on the MCUboot code for this
168 the development keys in the repo are never used in a production
177 There are bug fixes, and associated imgtool updates as well.
217 later boot stages. There are bug fixes, and associated imgtool
255 scratch partition. There are also lots of bug fixes, extra simulator
289 If multiple images and dependencies are not used, the images will be
312 There are no breaking changes in functionality. This release should work with
324 multi-images, and a new name for slot0/slot1 which are now called
[all …]
|
| D | readme-mbed.md | 15 * `"mcuboot.slot-size"`: size of an image slot (only one image, two slots are currently supported)
19 …boot/tree/main/boot/mbed/mbed_lib.json). Please note that certain features are not currently suppo…
25 …ted read and write sizes (granularities) are _no larger than_ 16 byte, which MCUboot's read/write …
|
| D | design.md | 67 /** Image header. All fields are in little endian byte order. */
123 Optional type-length-value records (TLVs) containing image metadata are placed
127 If protected TLVs are present then a TLV info header with magic equal to
162 The bootloader area contains the bootloader image itself. The other areas are
164 images therefore the flash area IDs of primary and secondary areas are mapped
195 scratch for your use case the following parameters are relevant:
201 that are actually used for storing the image are copied. The image/scratch ratio
227 slot areas sizes are equal.
250 4. Repeats steps 2. and 3. until all the slots' sectors are swapped.
255 larger than the secondary slot, although same-sized slots are allowed as well.
[all …]
|
| D | release.md | 11 1. MAJOR version when there are incompatible API changes.
14 3. PATCH version when there are backward-compatible bug fixes.
35 Before each release, tags are made (see below) for at least one
41 that should be merged into the main branch are those to fix bugs found
55 under test, while numbers are accepted only for the final releases.
|
| /mcuboot-3.6.0/boot/cypress/ |
| D | README.md | 5 …are created per MCUboot library maintainers requirements. Implemetation differs from conventional …
7 Examples provided to use with **ModusToolbox® Software Environment** are a recommended reference po…
16 There are two applications implemented:
42 Those are represented as submodules.
61 …d and upload MCUBootApp bootloader application and sample user applocation are located in `Readme.…
71 Following CLI / IDE are supported for project build:
|
| /mcuboot-3.6.0/ext/tinycrypt/lib/include/tinycrypt/ |
| D | ecc_platform_specific.h | 7 * modification, are permitted provided that the following conditions are met:
17 * ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE
30 * modification, are permitted provided that the following conditions are met:
46 * ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
|
| D | ecc_dh.h | 8 * modification, are permitted provided that the following conditions are met:
20 * ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE
33 * modification, are permitted provided that the following conditions are met:
49 * ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
|
| D | cbc_mode.h | 7 * modification, are permitted provided that the following conditions are met:
23 * ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
39 * cipher to provide confidentiality of strings whose lengths are
52 * methods for generating IVs are acceptable, provided that the
128 * @note Assumes:- in == iv + ciphertext, i.e. the iv and the ciphertext are
|
| D | ecc_dsa.h | 8 * modification, are permitted provided that the following conditions are met:
20 * ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE
34 * modification, are permitted provided that the following conditions are met:
50 * ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
|
| D | utils.h | 7 * modification, are permitted provided that the following conditions are met:
23 * ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
82 * @brief Constant-time algorithm to compare if two sequences of bytes are equal
|
| /mcuboot-3.6.0/ext/tinycrypt/ |
| D | LICENSE | 11 are permitted provided that the following conditions are met:
27 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
43 are permitted provided that the following conditions are met:
52 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
|
| /mcuboot-3.6.0/ext/tinycrypt/lib/source/ |
| D | ecc_platform_specific.c | 7 * modification, are permitted provided that the following conditions are met:
17 * ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE
30 * modification, are permitted provided that the following conditions are met:
46 * ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
|
| /mcuboot-3.6.0/ext/tinycrypt/tests/include/ |
| D | test_ecc_utils.h | 7 * modification, are permitted provided that the following conditions are met:
17 * ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE
30 * modification, are permitted provided that the following conditions are met:
46 * ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
|
| /mcuboot-3.6.0/boot/cypress/BlinkyApp/ |
| D | Readme.md | 23 …o demonstrate MCUboot library features and not as reference examples some considerations are taken.
25 1. Port/pin `P5_0` and `P5_1` used to configure serial port for debug prints. These pins are the mo…
31 These values are set by specifing following macros: `-DUSER_APP_SIZE`, `-DUSER_APP_START`, `-DRAM_S…
82 *Note:* only 2 images are supported at the moment.
110 …ready placed corresponing `*.pem` key in `\keys` folder. The key variables are defined in root `Ma…
116 Flags passed to `imgtool` for signature are defined in `SIGN_ARGS` variable in BlinkyApp.mk.
126 …ot` directory and `BlinkyApp_upgrade.hex` in `upgrade` folder. These files are ready to be flashed…
130 Files to use for programming are:
|
| /mcuboot-3.6.0/boot/mynewt/mcuboot_config/ |
| D | syscfg.yml | 29 description: 'Images are signed using RSA.'
35 description: 'Images are signed using ECDSA NIST P-256.'
38 description: 'Images are signed using ED25519.'
74 description: 'Maximum number of sectors that are swapped.'
79 - none downgrades are allowed
124 Default console log level. Valid values are:
|
| /mcuboot-3.6.0/ext/tinycrypt/documentation/ |
| D | tinycrypt.rst | 16 security and technicalities of each cryptographic primitive are found in the
92 peculiarities would increase the code size and thus are not considered here.
104 Some of these limitations are inherent to the cryptographic primitives
105 themselves, while others are specific to TinyCrypt. These limitations were accepted
108 limitations are discussed in-depth below.
140 be changed in future versions of the library as there are applications
177 * TinyCrypt CBC decryption assumes that the iv and the ciphertext are
195 * There are a few tradeoffs for the selection of the parameters of CCM mode.
198 invocations. Both things are related to the parameter 'q' of CCM mode. The
205 implications of this choice are:
[all …]
|
| /mcuboot-3.6.0/boot/bootutil/include/bootutil/ |
| D | bench.h | 35 * These are simple barrier-type benchmarks. If a platform has
36 * benchmarks that are enabled, calling `boot_bench_start()` before a
39 * The details of what is measured and how it is printed are specific
57 /* Without benchmarking enabled, these are just empty. */
|
| /mcuboot-3.6.0/docs/release-notes.d/ |
| D | 00readme.md | 12 Release notes are generally not needed for:
20 Release notes are included in files under this `docs/release-notes.d`
27 are not used for anything in particular, but to keep the files
|
| /mcuboot-3.6.0/boot/zcbor/include/ |
| D | zcbor_common.h | 105 and this keeps count of how many elements are
122 current map are being counted. */
129 map should not be searched. These are manipulated
236 #define ZCBOR_VALUE_IN_HEADER 23 ///! Values below this are encoded directly in the header.
313 * If there is no struct zcbor_state_constant (n_states == 1), error codes are
316 * payload, payload_len, elem_count, and elem_state are used to initialize the first state.
402 /** Check that the provided fragments are complete and in the right order.
411 * @retval true If the fragments are in the right order, and there are no
413 * @retval false If not all fragments have the same total_len, or gaps are
421 * The fragments are copied in the order they appear, without regard for
[all …]
|
| /mcuboot-3.6.0/boot/cypress/MCUBootApp/ |
| D | README.md | 7 There are two applications implemented:
31 **Important**: make sure primary, secondary slot and bootloader app sizes are appropriate and corre…
89 In multi-image operation (two images are considered for simplicity) MCUboot Bootloader application …
95 * Boots Primary_1 only if both - Primary_1 and Primary_2 are present and valid;
97 This ensures two dependent applications can be accepted by device only in case both images are vali…
120 …o demonstrate MCUboot library features and not as reference examples some considerations are taken.
142 …er. Same approach used in sample BlinkyLedApp application. Example command are provided below for …
172 There are couple ways of programming hex of MCUBootApp and BlinkyApp. Following instructions assume…
|
| /mcuboot-3.6.0/boot/cypress/MCUBootApp/config/ |
| D | mcuboot_crypto_config.h | 126 * The time does not need to be correct, only time differences are used,
188 * This makes sure there are no linking errors on platforms that do not support
271 * values are fully controlled by the application (such as pointers).
274 * parameters that are fully controlled by the application, and should always
331 * This section sets support for features that are or are not needed
332 * within the modules that are enabled.
368 * \warning MD2, MD4, MD5, ARC4, DES and SHA-1 are considered weak and their
426 * \note Because of a signature change, the core AES encryption and decryption routines are
439 * \warning MD2, MD4, MD5, DES and SHA-1 are considered weak and their use
488 * The functions mbedtls_internal_ecp_init and mbedtls_internal_ecp_free are
[all …]
|
