Home
last modified time | relevance | path

Searched refs:algorithm (Results 1 – 22 of 22) sorted by relevance

/rk3399_ARM-atf/tools/cert_create/src/
H A Dext.c186 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()
/rk3399_ARM-atf/drivers/tpm/
H A Dtpm2_cmds.c143 uint16_t algorithm, const uint8_t *digest, in tpm_pcr_extend() argument
197 ret = tpm_update_buffer(&pcr_extend_cmd, algorithm, sizeof(algorithm)); in tpm_pcr_extend()
/rk3399_ARM-atf/include/drivers/tpm/
H A Dtpm2.h100 uint16_t algorithm, const uint8_t *digest,
/rk3399_ARM-atf/drivers/measured_boot/rse/
H A Drse_measured_boot.c32 # error Invalid Measured Boot algorithm.
H A Ddice_prot_env.c36 # error Invalid DPE hash algorithm.
/rk3399_ARM-atf/docs/design_documents/
H A Ddtpm_drivers.rst70 - ``MBOOT_TPM_HASH_ALG``: The hash algorithm to be used by the TPM, currently
71 the only supported algorithm is ``sha256``. As additional Discrete TPMs are
91 algorithm.
H A Drse.rst138 description, measurement algorithm, etc.). More info on measured boot service
268 - ``Measurement algorithm``: Optional. The hash algorithm which was used to
291 - ``Measurement algorithm``: must be the same as the previous call(s),
317 in RSE memory. Some of the fields have a static value (measurement algorithm),
342 ``Measurement algorithm`` and stores it in the ``rse_mboot_metadata`` field
370 - ``MBOOT_RSE_HASH_ALG``: Determine the hash algorithm to measure the images.
392 INFO: - algorithm : 2000009
407 INFO: - algorithm : 2000009
423 INFO: - algorithm : 2000009
731 - ``DPE_ALG_ID``: Determine the hash algorithm to measure the images. The
H A Dmeasured_boot_dtpm_poc.rst138 - ``MBOOT_TPM_HASH_ALG=sha256`` sets the hash algorithm to sha256, this is
139 the only algorithm supported by both TF-A Measured Boot and the SLB 9670
H A Dmeasured_boot_poc.rst436 SHA256 logs here, as this is the algorithm we used on TF-A for the measurements
/rk3399_ARM-atf/docs/design/
H A Dauth-framework.rst374 type of hash algorithm used as this information accompanies the hash. This
376 algorithm implementations.
395 algorithm AlgorithmIdentifier{PUBLIC-KEY,{PublicKeyAlgorithms}},
404 algorithm ALGORITHM.&id({IOSet}),
405 parameters ALGORITHM.&Type({IOSet}{@algorithm}) OPTIONAL
541 AUTH_PARAM_SIG_ALG, /* The image signature algorithm */
542 AUTH_PARAM_HASH, /* A hash (including the algorithm) */
585 auth_param_type_desc_t *alg; /* Signature algorithm */
768 - ``alg``: the signature algorithm used (obtained from current image)
925 key, the algorithm, the signature and the data that has been signed. Therefore,
[all …]
H A Dtrusted-board-boot-build.rst62 The hashing algorithm is selected by ``HASH_ALG``; sha256 is used if
70 and can be specified by ``ROT_KEY``. The hashing algorithm is selected by ``HASH_ALG``;
H A Dpsci-pd-tree.rst231 algorithm to parse the power domain descriptor exported by the platform to
H A Dtrusted-board-boot.rst42 On Arm development platforms, a hash of the ROTPK (hash algorithm selected by
H A Dfirmware-design.rst542 therefore BL31 uses locks based on Lamport's Bakery algorithm instead.
2302 It is a characteristic of Lamport's Bakery algorithm that the volatile per-CPU
2323 algorithm mentioned earlier. The bakery_lock structure only allocates the memory
/rk3399_ARM-atf/docs/components/
H A Dxlat-tables-lib-v2-design.rst103 details can be found in `The memory mapping algorithm`_ section below).
339 The memory mapping algorithm
342 The mapping function is implemented as a recursive algorithm. It is however
346 By default [#granularity]_, the algorithm will attempt to minimize the
375 about the sorting algorithm in use.
H A Dgranule-protection-tables-design.rst73 whatever way is best for a given platform, either through some algorithm or hard
H A Drmm-el3-comms-spec.rst516 …``E_RMM_INVAL``,``CSize`` does not represent the size of a supported SHA algorithm for the first c…
1349 | hash_alg_id | 24 | uint32_t | Hash algorithm for data in `hash_buf` |
1354 | | | | defined by hash algorithm `hash_alg_id` |
/rk3399_ARM-atf/docs/plat/arm/
H A Darm-build-options.rst70 The hashing algorithm is selected by ``HASH_ALG``; sha256 is used if
77 he hashing algorithm is selected by ``HASH_ALG``; sha256 is used if ``HASH_ALG``
/rk3399_ARM-atf/docs/getting_started/
H A Dbuild-options.rst226 authenticated decryption algorithm to be used to decrypt firmware/s during
783 - ``KEY_ALG``: This build flag enables the user to select the algorithm to be
787 RSA 1.5 algorithm which is not TBBR compliant and is retained only for
792 the algorithm specified by ``KEY_ALG``. The valid values for ``KEY_SIZE``
793 depend on the chosen algorithm and the cryptographic module.
808 algorithm. It accepts 3 values: ``sha256``, ``sha384`` and ``sha512``.
850 - ``MBOOT_TPM_HASH_ALG``: Build flag to select the TPM hash algorithm used during
851 Measured Boot. Currently only accepts ``sha256`` as a valid algorithm.
/rk3399_ARM-atf/docs/
H A Dporting-guide.rst656 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
H A Dchange-log.md3953 …- for TPM features fw hash algorithm should be 16-bits ([c86cfa3](https://review.trustedfirmware.o…
/rk3399_ARM-atf/docs/threat_model/firmware_threat_model/
H A Dthreat_model.rst912 In addition to these, other metadata attributes (image version, hash algorithm