| /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/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 | 592 therefore BL31 uses locks based on Lamport's Bakery algorithm instead.
2122 It is a characteristic of Lamport's Bakery algorithm that the volatile per-CPU
2143 algorithm mentioned earlier. The bakery_lock structure only allocates the memory
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/design/ |
| A D | auth-framework.rst.txt | 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.txt | 231 algorithm to parse the power domain descriptor exported by the platform to
|
| A D | firmware-design.rst.txt | 592 therefore BL31 uses locks based on Lamport's Bakery algorithm instead.
2122 It is a characteristic of Lamport's Bakery algorithm that the volatile per-CPU
2143 algorithm mentioned earlier. The bakery_lock structure only allocates the memory
|
| /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 | granule-protection-tables-design.rst | 70 whatever way is best for a given platform, either through some algorithm or hard
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/components/ |
| A D | xlat-tables-lib-v2-design.rst.txt | 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.txt | 70 whatever way is best for a given platform, either through some algorithm or hard
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/getting_started/ |
| A D | build-options.rst.txt | 192 authenticated decryption algorithm to be used to decrypt firmware/s during
469 - ``KEY_ALG``: This build flag enables the user to select the algorithm to be
472 ``rsa_1_5`` is the legacy PKCS#1 RSA 1.5 algorithm which is not TBBR
477 the algorithm specified by ``KEY_ALG``. The valid values for ``KEY_SIZE``
478 depend on the chosen algorithm and the cryptographic module.
492 algorithm. It accepts 3 values: ``sha256``, ``sha384`` and ``sha512``.
|
| A D | porting-guide.rst.txt | 701 algorithm OBJECT IDENTIFIER,
702 parameters ANY DEFINED BY algorithm OPTIONAL
706 algorithm AlgorithmIdentifier,
|
| /trusted-firmware-a/docs/getting_started/ |
| A D | build-options.rst | 192 authenticated decryption algorithm to be used to decrypt firmware/s during
469 - ``KEY_ALG``: This build flag enables the user to select the algorithm to be
472 ``rsa_1_5`` is the legacy PKCS#1 RSA 1.5 algorithm which is not TBBR
477 the algorithm specified by ``KEY_ALG``. The valid values for ``KEY_SIZE``
478 depend on the chosen algorithm and the cryptographic module.
492 algorithm. It accepts 3 values: ``sha256``, ``sha384`` and ``sha512``.
|
| A D | porting-guide.rst | 701 algorithm OBJECT IDENTIFIER,
702 parameters ANY DEFINED BY algorithm OPTIONAL
706 algorithm AlgorithmIdentifier,
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/plat/arm/ |
| A D | arm-build-options.rst.txt | 74 ``plat/arm/board/common/rotpk/*_sha256.bin`` depending on the specified algorithm.
|
| /trusted-firmware-a/docs/plat/arm/ |
| A D | arm-build-options.rst | 74 ``plat/arm/board/common/rotpk/*_sha256.bin`` depending on the specified algorithm.
|
| /trusted-firmware-a/docs/build/latex/ |
| A D | sphinxlatextables.sty | 178 % paragraphs to be taken into account sanely by tabulary algorithm for column
185 % incorporate the contents in its algorithm. But then we must clear the
|
| A D | trustedfirmware-a.tex | 3980 authenticated decryption algorithm to be used to decrypt firmware/s during
4366 depend on the chosen algorithm and the cryptographic module.
6330 \PYG{n}{algorithm} \PYG{n}{AlgorithmIdentifier}\PYG{p}{,}
23446 \subsubsection{The memory mapping algorithm}
23459 \end{footnote}, the algorithm will attempt to minimize the
23492 about the sorting algorithm in use.
25374 algorithm implementations.
26119 extract the signature algorithm from the certificate.
26223 The mbedTLS library algorithm support is configured by both the
26241 on AES\sphinxhyphen{}GCM algorithm. Valid values are 0 and 1.
[all …]
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/design_documents/ |
| A D | measured_boot_poc.rst.txt | 434 SHA256 logs here, as this is the algorithm we used on TF-A for the measurements
|
| /trusted-firmware-a/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
|
| /trusted-firmware-a/docs/build/TF-A_2.5/ |
| A D | searchindex.js | 1 …algorithm:[18,36,38,41,43,47,48,53,66,131],algorithmid:47,algorithmidentifi:[36,53],alia:[47,131],…
|