Searched refs:algorithm (Results 1 – 13 of 13) sorted by relevance
| /arm-trusted-firmware-2.8.0/tools/cert_create/src/ |
| A D | ext.c | 186 ASN1_OBJECT *algorithm; in ext_new_hash() local
197 algorithm = OBJ_nid2obj(EVP_MD_type(md)); in ext_new_hash()
198 if (algorithm == NULL) { in ext_new_hash()
204 hash->hashAlgorithm->algorithm = algorithm; in ext_new_hash()
|
| /arm-trusted-firmware-2.8.0/drivers/measured_boot/rss/ |
| A D | rss_measured_boot.c | 32 # error Invalid Measured Boot algorithm.
|
| /arm-trusted-firmware-2.8.0/docs/design/ |
| A D | auth-framework.rst | 305 type of hash algorithm used as this information accompanies the hash. This
307 algorithm implementations.
335 algorithm ALGORITHM.&id({IOSet}),
336 parameters ALGORITHM.&Type({IOSet}{@algorithm}) OPTIONAL
472 AUTH_PARAM_SIG_ALG, /* The image signature algorithm */
473 AUTH_PARAM_HASH, /* A hash (including the algorithm) */
515 auth_param_type_desc_t *alg; /* Signature algorithm */
698 - ``alg``: the signature algorithm used (obtained from current image)
867 extract the signature algorithm from the certificate.
956 The mbedTLS library algorithm support is configured by both the
[all …]
|
| A D | psci-pd-tree.rst | 231 algorithm to parse the power domain descriptor exported by the platform to
|
| A D | firmware-design.rst | 595 therefore BL31 uses locks based on Lamport's Bakery algorithm instead.
2145 It is a characteristic of Lamport's Bakery algorithm that the volatile per-CPU
2166 algorithm mentioned earlier. The bakery_lock structure only allocates the memory
|
| /arm-trusted-firmware-2.8.0/drivers/measured_boot/event_log/ |
| A D | event_log.c | 26 # error Invalid TPM algorithm.
|
| /arm-trusted-firmware-2.8.0/docs/components/ |
| A D | xlat-tables-lib-v2-design.rst | 109 details can be found in `The memory mapping algorithm`_ section below).
356 The memory mapping algorithm
359 The mapping function is implemented as a recursive algorithm. It is however
363 By default [#granularity]_, the algorithm will attempt to minimize the
392 about the sorting algorithm in use.
394 This mapping algorithm does not apply to the MPU library, since the MPU hardware
|
| A D | granule-protection-tables-design.rst | 70 whatever way is best for a given platform, either through some algorithm or hard
|
| A D | rmm-el3-comms-spec.rst | 480 ``E_RMM_INVAL``,``CSize`` does not represent the size of a supported SHA algorithm
|
| /arm-trusted-firmware-2.8.0/docs/plat/arm/ |
| A D | arm-build-options.rst | 74 ``plat/arm/board/common/rotpk/*_sha256.bin`` depending on the specified algorithm.
|
| /arm-trusted-firmware-2.8.0/docs/getting_started/ |
| A D | build-options.rst | 201 authenticated decryption algorithm to be used to decrypt firmware/s during
611 - ``KEY_ALG``: This build flag enables the user to select the algorithm to be
615 RSA 1.5 algorithm which is not TBBR compliant and is retained only for
620 the algorithm specified by ``KEY_ALG``. The valid values for ``KEY_SIZE``
621 depend on the chosen algorithm and the cryptographic module.
640 algorithm. It accepts 3 values: ``sha256``, ``sha384`` and ``sha512``.
|
| A D | porting-guide.rst | 578 size of the Event Log buffer, depending upon the highest hash algorithm
723 algorithm OBJECT IDENTIFIER,
724 parameters ANY DEFINED BY algorithm OPTIONAL
728 algorithm AlgorithmIdentifier,
940 containing PCR usage schema, TPM-based hash, and firmware hash algorithm
|
| /arm-trusted-firmware-2.8.0/docs/design_documents/ |
| A D | measured_boot_poc.rst | 434 SHA256 logs here, as this is the algorithm we used on TF-A for the measurements
|
Completed in 33 milliseconds