Searched refs:signature (Results 1 – 25 of 58) sorted by relevance
123
| /Zephyr-latest/subsys/jwt/ |
| D | Kconfig | 14 prompt "JWT signature algorithm"
20 bool "Use RSA signature (RS-256). Use Mbed TLS as crypto library."
26 bool "Use RSA signature (RS-256). Use PSA Crypto API."
35 bool "Use ECDSA signature (ES-256). Use PSA Crypto API."
|
| /Zephyr-latest/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.
|
| /Zephyr-latest/scripts/pylib/pytest-twister-harness/src/twister_harness/helpers/ |
| D | shell.py | 12 from inspect import signature
122 cls_fields = {field for field in signature(cls).parameters}
|
| /Zephyr-latest/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.
|
| /Zephyr-latest/include/zephyr/acpi/ |
| D | acpi.h | 234 void *acpi_table_get(char *signature, int inst);
|
| /Zephyr-latest/soc/nxp/imxrt/imxrt118x/ |
| D | Kconfig | 42 format consists container header, image arrary entry, signature block
|
| /Zephyr-latest/modules/ |
| D | Kconfig.tinycrypt | 53 bool "ECC_DSA digital signature algorithm"
|
| /Zephyr-latest/boards/starfive/visionfive2/doc/ |
| D | index.rst | 23 is a jh7110 signature tool used to generate spl header information
|
| /Zephyr-latest/doc/hardware/peripherals/sensor/ |
| D | fetch_and_get.rst | 43 a function signature matching :c:type:`sensor_trigger_handler_t` using
|
| /Zephyr-latest/cmake/linker/lld/ |
| D | target.cmake | 113 # signature to ensure that standard c and runtime libraries are correctly placed
|
| /Zephyr-latest/boards/waveshare/esp32s3_touch_lcd_1_28/doc/ |
| D | index.rst | 45 - Cryptographic hardware acceleration: (AES-128/256, Hash, RSA, RNG, HMAC, Digital signature)
|
| /Zephyr-latest/drivers/dma/ |
| D | dma_iproc_pax.h | 443 uint32_t signature:16; member
|
| /Zephyr-latest/doc/releases/ |
| D | migration-guide-4.0.rst | 567 * By default, the signature is now computed using the PSA Crypto API for both RSA and ECDSA
573 * The following new symbols were added to allow specifying both the signature
576 * :kconfig:option:`CONFIG_JWT_SIGN_RSA_PSA` (default) RSA signature using the PSA Crypto API;
577 * :kconfig:option:`CONFIG_JWT_SIGN_RSA_LEGACY` RSA signature using Mbed TLS;
578 * :kconfig:option:`CONFIG_JWT_SIGN_ECDSA_PSA` ECDSA signature using the PSA Crypto API.
|
| 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,
287 * The ``accept()`` callback's signature in :c:struct:`bt_l2cap_server` has
|
| /Zephyr-latest/doc/services/retention/ |
| D | blinfo.rst | 107 * ``blinfo/signature_type`` The signature type MCUboot is configured for
|
| /Zephyr-latest/boards/intel/adsp/doc/ |
| D | chromebooks_adsp.rst | 77 Now you need to turn of signature verification in the bootloader
78 (because obviously we'll be breaking whatever signature existed).
79 Note that signature verification is something done by the ROM
294 there because the boot requires a valid signature, even though as
|
| /Zephyr-latest/doc/ |
| D | CMakeLists.txt | 81 # This function has the same signature as `add_custom_target()`
|
| /Zephyr-latest/lib/acpi/ |
| D | acpi.c | 648 void *acpi_table_get(char *signature, int inst) in acpi_table_get() argument
661 status = AcpiGetTable(signature, inst, &table); in acpi_table_get()
|
| /Zephyr-latest/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-latest/doc/services/llext/ |
| D | load.rst | 49 signature that is compatible with the :c:func:`k_thread_create` API, and will
|
| /Zephyr-latest/scripts/ci/ |
| D | pylintrc | 113 unexpected-special-method-signature,
|
| /Zephyr-latest/doc/develop/api/ |
| D | design_guidelines.rst | 15 specifying the signature of a callback:
|
| /Zephyr-latest/share/sysbuild/images/bootloader/ |
| D | Kconfig | 129 bool "No signature; use only hash check"
|
| /Zephyr-latest/cmake/modules/ |
| D | FindZephyr-sdk.cmake | 11 # Its purpose is to allow the find_package basic signature mode to lookup Zephyr
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | net_mgmt.rst | 182 You define your handler modeled with this signature:
|
123
