Searched refs:algorithm (Results 1 – 14 of 14) sorted by relevance
/trusted-firmware-a-latest/tools/cert_create/src/ |
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-latest/drivers/measured_boot/rss/ |
D | rss_measured_boot.c | 32 # error Invalid Measured Boot algorithm.
|
/trusted-firmware-a-latest/docs/design/ |
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. 364 algorithm AlgorithmIdentifier{PUBLIC-KEY,{PublicKeyAlgorithms}}, 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) */ 553 auth_param_type_desc_t *alg; /* Signature algorithm */ 736 - ``alg``: the signature algorithm used (obtained from current image) [all …]
|
D | psci-pd-tree.rst | 231 algorithm to parse the power domain descriptor exported by the platform to
|
D | firmware-design.rst | 542 therefore BL31 uses locks based on Lamport's Bakery algorithm instead. 2242 It is a characteristic of Lamport's Bakery algorithm that the volatile per-CPU 2263 algorithm mentioned earlier. The bakery_lock structure only allocates the memory
|
/trusted-firmware-a-latest/docs/design_documents/ |
D | rss.rst | 132 description, measurement algorithm, etc.). More info on measured boot service 257 - ``Measurement algorithm``: Optional. The hash algorithm which was used to 280 - ``Measurement algorithm``: must be the same as the previous call(s), 306 in RSS memory. Some of the fields have a static value (measurement algorithm), 331 ``Measurement algorithm`` and stores it in the ``rss_mboot_metadata`` field 361 - ``MBOOT_RSS_HASH_ALG``: Determine the hash algorithm to measure the images. 383 INFO: - algorithm : 2000009 398 INFO: - algorithm : 2000009 414 INFO: - algorithm : 2000009
|
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-latest/drivers/measured_boot/event_log/ |
D | event_log.c | 24 # error Invalid TPM algorithm.
|
/trusted-firmware-a-latest/docs/components/ |
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
|
D | granule-protection-tables-design.rst | 70 whatever way is best for a given platform, either through some algorithm or hard
|
D | rmm-el3-comms-spec.rst | 483 ``E_RMM_INVAL``,``CSize`` does not represent the size of a supported SHA algorithm
|
/trusted-firmware-a-latest/docs/plat/arm/ |
D | arm-build-options.rst | 79 algorithm. Providing ``ROT_KEY`` enforces generation of the hash from the
|
/trusted-firmware-a-latest/docs/getting_started/ |
D | build-options.rst | 207 authenticated decryption algorithm to be used to decrypt firmware/s during 614 - ``KEY_ALG``: This build flag enables the user to select the algorithm to be 618 RSA 1.5 algorithm which is not TBBR compliant and is retained only for 623 the algorithm specified by ``KEY_ALG``. The valid values for ``KEY_SIZE`` 624 depend on the chosen algorithm and the cryptographic module. 639 algorithm. It accepts 3 values: ``sha256``, ``sha384`` and ``sha512``.
|
/trusted-firmware-a-latest/docs/ |
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
|