Home
last modified time | relevance | path

Searched refs:certificates (Results 1 – 25 of 27) sorted by relevance

12

/rk3399_ARM-atf/docs/components/
H A Dcot-binding.rst44 In other words, certificates which are validated
59 This property is required for all non-root certificates.
61 This property is not required for root-certificates
62 as root-certificates are validated using root of trust
70 For non-root certificates, this property is used to refer
72 required property for all non-root certificates which are
75 This property is not required for all root-certificates. If
86 This property is used by all certificates which are
332 Description: Contains root-of-trust keys for the root certificates.
337 Root of trust key information present in the root certificates
[all …]
H A Dfirmware-update.rst177 authentication). Secure world certificates and non-AP images are examples
/rk3399_ARM-atf/docs/design/
H A Dtrusted-board-boot.rst51 The remaining components in the CoT are either certificates or boot loader
52 images. The certificates follow the `X.509 v3`_ standard. This standard
53 enables adding custom extensions to the certificates, which are used to store
56 All certificates are self-signed. There is no need for a Certificate Authority
59 the certificates, different signature schemes are available, please refer to the
62 The certificates are categorised as "Key" and "Content" certificates. Key
63 certificates are used to verify public keys which have been used to sign content
64 certificates. Content certificates are used to store the hash of a boot loader
69 extension fields in the `X.509 v3`_ certificates.
79 In the TBBR CoT, all firmware binaries and certificates are (directly or
[all …]
H A Dtrusted-board-boot-build.rst98 FIP will include the certificates corresponding to the selected Chain of
99 Trust. These certificates can also be found in the output build directory.
134 Both the FIP and FWU_FIP will include the certificates corresponding to the
135 selected Chain of Trust. These certificates can also be found in the output
H A Dauth-framework.rst15 X.509v3 certificates to ferry Subject Public Keys, hashes and non-volatile
288 The ``_verify_signature`` function is used to verify certificates,
330 x509v3 certificates, signed ELF files or any other platform specific format).
445 PKI certificates (authentication images). It is expected that open source
710 The TBBR specifies the additional certificates that must accompany these images
715 identifiers for all the images and certificates that will be loaded during the
741 (i.e. the BL2 and Trusted Key certificates are signed with the ROT private
778 extracted from the certificates. In the case of the TBBR CoT, these parameters
/rk3399_ARM-atf/plat/nxp/common/fip_handler/fuse_fip/
H A Dfuse.mk60 …$(error Error: Trusted Board Boot with X509 certificates not supported with FUSE_PROG build option)
/rk3399_ARM-atf/docs/plat/nxp/
H A Dnxp-ls-tbbr.rst42 Option 1: CoT using X 509 certificates
57 - SAVE_KEYS=1 saves the keys and certificates, if GENERATE_COT=1.
63 - ROTPK for x.509 certificates is generated and embedded in bl2.bin and
/rk3399_ARM-atf/plat/nxp/common/tbbr/
H A Dtbbr.mk132 certificates: $(ROT_KEY)
/rk3399_ARM-atf/plat/imx/imx7/common/
H A Dimx7.mk78 certificates: $(ROT_KEY)
/rk3399_ARM-atf/plat/socionext/uniphier/
H A Dplatform.mk108 certificates: $(ROT_KEY)
/rk3399_ARM-atf/plat/socionext/synquacer/
H A Dplatform.mk83 certificates: $(ROT_KEY)
/rk3399_ARM-atf/plat/hisilicon/hikey/
H A Dplatform.mk155 certificates: $(ROT_KEY)
/rk3399_ARM-atf/plat/imx/imx8m/imx8mp/
H A Dplatform.mk131 certificates: $(ROT_KEY)
/rk3399_ARM-atf/docs/tools/
H A Dcot-dt2c.rst91 the certificates and the image of a CoT DT file.
/rk3399_ARM-atf/plat/hisilicon/hikey960/
H A Dplatform.mk148 certificates: $(ROT_KEY)
/rk3399_ARM-atf/docs/components/fconf/
H A Dtb_fw_bindings.rst141 node containing ``manifests`` and ``images`` sub-nodes, with certificates,
/rk3399_ARM-atf/plat/imx/imx8m/imx8mm/
H A Dplatform.mk134 certificates: $(ROT_KEY)
/rk3399_ARM-atf/plat/qemu/qemu/
H A Dplatform.mk77 certificates: $(ROT_KEY)
/rk3399_ARM-atf/plat/rpi/rpi3/
H A Dplatform.mk265 certificates: $(ROT_KEY)
/rk3399_ARM-atf/
H A DMakefile443 FIP_DEPS += certificates
1169 certificates: ${CRT_DEPS} ${CRTTOOL} ${DTBS} target
/rk3399_ARM-atf/docs/security_advisories/
H A Dsecurity-advisory-tfv-10.rst41 parse boot certificates in TF-A trusted boot: it is possible for a crafted
/rk3399_ARM-atf/docs/plat/
H A Dwarp7.rst78 BL33=fiptool_images/u-boot.bin certificates all
/rk3399_ARM-atf/docs/plat/arm/
H A Darm-build-options.rst68 to sign the BL2 and Trusted Key certificates. Available options for
/rk3399_ARM-atf/docs/getting_started/
H A Dbuild-options.rst717 tool to create certificates as per the Chain of Trust described in
719 include the certificates in the FIP and FWU_FIP. Default value is '0'.
723 the corresponding certificates, and to include those certificates in the
728 include the corresponding certificates. This FIP can be used to verify the
733 will not include the corresponding certificates, causing a boot failure.
1115 and verify the certificates and images in a FIP, and BL1 includes support
1117 of certificates in the FIP and FWU_FIP depends upon the value of the
/rk3399_ARM-atf/docs/threat_model/
H A Dsupply_chain_threat_model.rst59 - *cert_create*: This tool is used to generate certificates for binary images.

12