Searched refs:algorithm (Results 1 – 17 of 17) sorted by relevance
| /trusted-firmware-a/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()
|
| /trusted-firmware-a/drivers/measured_boot/rse/ |
| A D | rse_measured_boot.c | 32 # error Invalid Measured Boot algorithm.
|
| A D | dice_prot_env.c | 36 # error Invalid DPE hash algorithm.
|
| /trusted-firmware-a/docs/design/ |
| A D | auth-framework.rst | 266 return the hash of the given data using the provided hash algorithm.
343 type of hash algorithm used as this information accompanies the hash. This
345 algorithm implementations.
373 algorithm ALGORITHM.&id({IOSet}),
374 parameters ALGORITHM.&Type({IOSet}{@algorithm}) OPTIONAL
510 AUTH_PARAM_SIG_ALG, /* The image signature algorithm */
511 AUTH_PARAM_HASH, /* A hash (including the algorithm) */
554 auth_param_type_desc_t *alg; /* Signature algorithm */
906 extract the signature algorithm from the certificate.
998 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 | 542 therefore BL31 uses locks based on Lamport's Bakery algorithm instead.
2275 It is a characteristic of Lamport's Bakery algorithm that the volatile per-CPU
2296 algorithm mentioned earlier. The bakery_lock structure only allocates the memory
|
| /trusted-firmware-a/docs/design_documents/ |
| A D | rse.rst | 132 description, measurement algorithm, etc.). More info on measured boot service
262 - ``Measurement algorithm``: Optional. The hash algorithm which was used to
285 - ``Measurement algorithm``: must be the same as the previous call(s),
311 in RSE memory. Some of the fields have a static value (measurement algorithm),
336 ``Measurement algorithm`` and stores it in the ``rse_mboot_metadata`` field
364 - ``MBOOT_RSE_HASH_ALG``: Determine the hash algorithm to measure the images.
386 INFO: - algorithm : 2000009
401 INFO: - algorithm : 2000009
417 INFO: - algorithm : 2000009
725 - ``DPE_ALG_ID``: Determine the hash algorithm to measure the images. The
|
| A D | measured_boot_poc.rst | 436 SHA256 logs here, as this is the algorithm we used on TF-A for the measurements
|
| /trusted-firmware-a/drivers/measured_boot/event_log/ |
| A D | event_log.c | 24 # error Invalid TPM algorithm.
|
| /trusted-firmware-a/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 | rmm-el3-comms-spec.rst | 505 …``E_RMM_INVAL``,``CSize`` does not represent the size of a supported SHA algorithm for the first c…
845 | hash_alg_id | 24 | uint32_t | Hash algorithm for data in `hash_buf` |
850 | | | | defined by hash algorithm `hash_alg_id` |
|
| A D | granule-protection-tables-design.rst | 73 whatever way is best for a given platform, either through some algorithm or hard
|
| /trusted-firmware-a/docs/plat/arm/ |
| A D | arm-build-options.rst | 85 algorithm. Providing ``ROT_KEY`` enforces generation of the hash from the
|
| /trusted-firmware-a/docs/getting_started/ |
| A D | build-options.rst | 218 authenticated decryption algorithm to be used to decrypt firmware/s during
711 - ``KEY_ALG``: This build flag enables the user to select the algorithm to be
715 RSA 1.5 algorithm which is not TBBR compliant and is retained only for
720 the algorithm specified by ``KEY_ALG``. The valid values for ``KEY_SIZE``
721 depend on the chosen algorithm and the cryptographic module.
736 algorithm. It accepts 3 values: ``sha256``, ``sha384`` and ``sha512``.
|
| /trusted-firmware-a/docs/ |
| A D | porting-guide.rst | 656 size of the Event Log buffer, depending upon the highest hash algorithm
801 algorithm OBJECT IDENTIFIER,
802 parameters ANY DEFINED BY algorithm OPTIONAL
806 algorithm AlgorithmIdentifier,
990 containing PCR usage schema, TPM-based hash, and firmware hash algorithm
|
| A D | change-log.md | 1384 …- for TPM features fw hash algorithm should be 16-bits ([c86cfa3](https://review.trustedfirmware.o…
|
| /trusted-firmware-a/docs/threat_model/firmware_threat_model/ |
| A D | threat_model.rst | 911 In addition to these, other metadata attributes (image version, hash algorithm
|
Completed in 98 milliseconds