Lines Matching full:using

44 reading the internal flash memory, or using some attack vector that
47 Since decrypting requires a private key (or secret if using symmetric
62 The image is encrypted using AES-CTR-128 or AES-CTR-256, with a counter
74 encrypted using either RSA-OAEP, AES-KW (128 or 256 bits depending on the
90 * Generate a new private key and derive the public key; when using ECIES-P256
91   this is a secp256r1 keypair, when using ECIES-X25519 this will be a x25519
93 * Generate a new secret (DH) using the ephemeral private key and the public key
95 * Derive the new keys from the secret using HKDF (built on HMAC-SHA256). We
96   are not using a `salt` and using an `info` of `MCUBoot_ECIES_v1`, generating
100 * The key is encrypted with AES-128-CTR or AES-256-CTR and a `nonce` of 0 using
102 * The encrypted key now goes through a HMAC-SHA256 using the remaining 32
123 If swap using scratch is used for the upgrade process, the decryption happens
152 `imgtool` can generate keys by using `imgtool keygen -k <output.pem> -t <type>`,
161 If using AES-KW, follow the steps in the next section to generate the
166 * If using RSA-OAEP, generate a keypair following steps similar to those
168 * If using ECIES-P256, generate a keypair following steps similar to those
170 * If using ECIES-X25519, generate a private key passing the option `-t x25519`
173 * If using AES-KW (`newt` only), the `kek` can be generated with a