| /Zephyr-Core-3.5.0/subsys/jwt/ |
| D | Kconfig | 11 prompt "JWT signature algorithm"
18 bool "Use RSA signature (RS-256)"
23 bool "Use ECDSA signature (ES-256)"
|
| /Zephyr-Core-3.5.0/cmake/ |
| D | target_toolchain_flags.cmake | 3 # What we are looking for, is a signature definition that is defined
12 # * CMAKE_C_COMPILER_ID is taking the CMake compiler id for extra signature.
14 # methods, where an upgraded compiler could have same signature due to ccache
16 # and thus generate a new signature.
18 # Toolchains with the same signature will always support the same set of flags.
23 # Extend the CMAKE_C_COMPILER_MD5_SUM with the compiler signature.
|
| D | mcuboot.cmake | 26 # No signature key file, no signed binaries. No error, though:
|
| /Zephyr-Core-3.5.0/arch/x86/core/ |
| D | acpi.c | 135 void *z_acpi_find_table(uint32_t signature) in z_acpi_find_table() argument
173 if (t->signature == signature && check_sum(t)) { in z_acpi_find_table()
215 if (t->signature == signature && check_sum(t)) { in z_acpi_find_table()
|
| /Zephyr-Core-3.5.0/cmake/linker/armlink/ |
| D | linker_flags.cmake | 1 # The ARMClang linker, armlink, requires a dedicated linking signature in
|
| /Zephyr-Core-3.5.0/scripts/pylib/pytest-twister-harness/src/twister_harness/helpers/ |
| D | shell.py | 12 from inspect import signature
98 cls_fields = {field for field in signature(cls).parameters}
|
| /Zephyr-Core-3.5.0/samples/tfm_integration/psa_crypto/ |
| D | CMakeLists.txt | 23 # insufficient memory failure while verifying signature. Increase it to 0x2400.
|
| D | README.rst | 40 - Verify the signature using the public key
333 [00:00:03.658,000] <inf> app: Verifying signature for SHA-256 hash
|
| /Zephyr-Core-3.5.0/include/zephyr/acpi/ |
| D | acpi.h | 142 void *acpi_table_get(char *signature, int inst);
|
| /Zephyr-Core-3.5.0/doc/services/device_mgmt/ |
| D | ota.rst | 44 is downloaded and installed. MCUboot can be used to verify the signature before
56 signature before upgrading the firmware.
|
| D | mcumgr.rst | 389 validate the image, using the SHA-256 and/or the signature (depending on
391 valid is to run ``imgtool verify -k <your-signature-key> <your-image>``,
392 where ``-k <your-signature-key`` can be skipped if no signature validation
|
| /Zephyr-Core-3.5.0/share/sysbuild/images/bootloader/ |
| D | Kconfig | 45 bool "No signature; use only hash check"
|
| /Zephyr-Core-3.5.0/modules/ |
| D | Kconfig.tinycrypt | 48 bool "ECC_DSA digital signature algorithm"
|
| /Zephyr-Core-3.5.0/drivers/dma/ |
| D | dma_iproc_pax.h | 443 uint32_t signature:16; member
|
| /Zephyr-Core-3.5.0/lib/acpi/ |
| D | acpi.c | 628 void *acpi_table_get(char *signature, int inst) in acpi_table_get() argument
641 status = AcpiGetTable(signature, inst, &table); in acpi_table_get()
|
| /Zephyr-Core-3.5.0/doc/services/retention/ |
| D | blinfo.rst | 107 * ``blinfo/signature_type`` The signature type MCUboot is configured for
|
| /Zephyr-Core-3.5.0/boards/xtensa/intel_adsp_cavs25/doc/ |
| D | chromebooks_adsp.rst | 79 Now you need to turn of signature verification in the bootloader
80 (because obviously we'll be breaking whatever signature existed).
81 Note that signature verification is something done by the ROM
296 there because the boot requires a valid signature, even though as
|
| /Zephyr-Core-3.5.0/cmake/modules/ |
| D | FindZephyr-sdk.cmake | 7 # Its purpose is to allow the find_package basic signature mode to lookup Zephyr
|
| /Zephyr-Core-3.5.0/doc/ |
| D | CMakeLists.txt | 69 # This function has the same signature as `add_custom_target()`
|
| /Zephyr-Core-3.5.0/doc/security/ |
| D | sensor-threat.rst | 151 The bootloader is responsible for verifying the signature of the
155 The bootloader shall verify the signature of the update image
163 this image, the bootloader shall verify a digital signature of the
234 certificate chain has a valid signature path from a root
|
| /Zephyr-Core-3.5.0/doc/releases/ |
| D | migration-guide-3.5.rst | 20 * The kernel :c:func:`k_mem_slab_free` function has changed its signature, now
22 The new signature will not immediately trigger a compiler error or warning,
258 * The ``accept()`` callback's signature in :c:struct:`bt_l2cap_server` has
|
| /Zephyr-Core-3.5.0/doc/develop/api/ |
| D | design_guidelines.rst | 15 specifying the signature of a callback:
|
| /Zephyr-Core-3.5.0/doc/services/crypto/ |
| D | tinycrypt.rst | 75 * Type of primitive: Digital signature.
255 * Digital signature (EC-DSA);
|
| /Zephyr-Core-3.5.0/scripts/ci/ |
| D | pylintrc | 114 unexpected-special-method-signature,
|
| /Zephyr-Core-3.5.0/doc/connectivity/networking/api/ |
| D | net_mgmt.rst | 142 You define your handler modeled with this signature:
|
