Searched refs:keys (Results 1 – 23 of 23) sorted by relevance
| /mcuboot-2.7.6/samples/zephyr/bad-keys/ |
| D | README.md | 1 # Bad keys for testing
3 This directory contains some alternate keys that can be used for
4 testing. Signing the images with either of these keys, but leaving
5 the demo keys's public keys in the bootloader should result in it not
|
| /mcuboot-2.7.6/scripts/imgtool/ |
| D | main.py | 23 import imgtool.keys as keys namespace
27 from .keys import (
37 keys.RSA.generate().export_private(path=keyfile, passwd=passwd)
41 keys.RSA.generate(key_size=3072).export_private(path=keyfile,
46 keys.ECDSA256P1.generate().export_private(keyfile, passwd=passwd)
54 keys.Ed25519.generate().export_private(path=keyfile, passwd=passwd)
58 keys.X25519.generate().export_private(path=keyfile, passwd=passwd)
74 key = keys.load(keyfile)
78 return keys.load(keyfile, passwd)
97 type=click.Choice(keygens.keys()), prompt=True,
[all …]
|
| D | image.py | 31 from .keys import rsa, ecdsa, x25519
|
| /mcuboot-2.7.6/ci/fih_test_docker/ |
| D | generate_test_report.py | 45 if "skipped" in test.keys() and not test["skipped"]:
64 for last_line in failed_boot_last_lines.keys():
68 for reason in exec_fail_reasons.keys():
|
| /mcuboot-2.7.6/boot/cypress/ |
| D | Makefile | 202 @echo Generate ECC256 keys: $(SIGN_KEY_FILE).pem and $(SIGN_KEY_FILE).pub
203 ../../scripts/imgtool.py keygen -k keys/$(SIGN_KEY_FILE).pem -t ecdsa-p256
204 ../../scripts/imgtool.py getpub -k keys/$(SIGN_KEY_FILE).pem > keys/$(SIGN_KEY_FILE).pub
|
| /mcuboot-2.7.6/docs/ |
| D | imgtool.md | 4 operations that are necessary to manage keys and sign images. Using
13 ## [Managing keys](#managing-keys)
15 This tool currently supports rsa-2048, rsa-3072, ecdsa-p256 and ed25519 keys.
38 For Zephyr, the keys live in the file `boot/zephyr/keys.c`. For
90 instead of plain keys. Enable when
|
| D | readme-zephyr.md | 104 keys. It is important to stress that these should never be used for
127 ## Managing signing keys
129 The signing keys used by MCUboot are represented in standard formats,
151 bootloader. The keys live in `boot/zephyr/keys.c`, and can be
159 directly into the `keys.c` file.
|
| D | testplan-mynewt.md | 12 key_<sign-algo>.pem, key_<sign-algo>_2.pem. And a keys file with the C public
35 * `newt create-image k64f_blinky2 1.0.2 <one-of-the-sign-keys-or-none>`
84 * `newt create-image k64f_blinky2 1.0.2 <bad and good rsa keys>.pem`
|
| D | SECURITY.md | 14 If you wish to send encrypted email, you may use these PGP keys:
|
| D | release-notes.md | 50 X25519 encrypted images, rollback protection, hardware keys, and a
67 - Add support for hardware keys.
104 - imgtool can dump private keys in C format (getpriv command), which
105 can be added as decryption keys. Optionally can remove superfluous
236 newt/imgtool support for password protected keys.
245 protected keys
|
| D | release.md | 57 new release version, including updates to the pseudo keys
|
| /mcuboot-2.7.6/scripts/imgtool/keys/ |
| D | rsa_test.py | 21 from imgtool.keys import load, RSA, RSAUsageError
22 from imgtool.keys.rsa import RSA_KEY_SIZES
|
| D | ecdsa_test.py | 19 from imgtool.keys import load, ECDSA256P1, ECDSAUsageError
|
| D | ed25519_test.py | 19 from imgtool.keys import load, Ed25519, Ed25519UsageError
|
| /mcuboot-2.7.6/scripts/ |
| D | assemble.py | 33 for ak in a.keys():
36 for bk in b.keys():
|
| /mcuboot-2.7.6/samples/zephyr/ |
| D | Makefile | 271 SIGNING_KEY=bad-keys/bad-rsa-2048.pem \
286 SIGNING_KEY=bad-keys/bad-ec-p256.pem \
|
| /mcuboot-2.7.6/sim/mcuboot-sys/src/ |
| D | c.rs | 36 for &dev_id in multiflash.keys() { in boot_go()
|
| /mcuboot-2.7.6/boot/cypress/BlinkyApp/ |
| D | BlinkyApp.mk | 103 … 8 -v "2.0" -S $(SLOT_SIZE) -M 512 --overwrite-only -R $(ERASED_VALUE) -k keys/$(SIGN_KEY_FILE).pem
|
| D | Readme.md | 110 This also suggests user already placed corresponing `*.pem` key in `\keys` folder. The key variable…
|
| /mcuboot-2.7.6/boot/zephyr/ |
| D | Kconfig | 248 bool "Save encrypted key TLVs instead of plaintext keys in swap metadata"
251 If y, instead of saving the encrypted image keys in plaintext in the
254 slot from being dumped. If n is selected (default), the keys are written
|
| D | CMakeLists.txt | 94 keys.c
|
| /mcuboot-2.7.6/ext/tinycrypt/documentation/ |
| D | tinycrypt.rst | 159 application is running in a constrained environment. AES-256 requires keys
266 * Construct keys (HMAC-SHA256);
|
| /mcuboot-2.7.6/boot/cypress/MCUBootApp/ |
| D | README.md | 162 …ding corresponding binary key data in `enc_priv_key[]` (file `\MCUBootApp\keys.c`). The public par…
|
