Home
last modified time | relevance | path

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

/arm-trusted-firmware-2.8.0/docs/design/
A Dtrusted-board-boot.rst29 The remaining components in the CoT are either certificates or boot loader
30 images. The certificates follow the `X.509 v3`_ standard. This standard
31 enables adding custom extensions to the certificates, which are used to store
34 In the TBB CoT all certificates are self-signed. There is no need for a
40 The certificates are categorised as "Key" and "Content" certificates. Key
42 certificates. Content certificates are used to store the hash of a boot loader
47 extension fields in the `X.509 v3`_ certificates.
58 The private part is used to sign the key certificates corresponding to the
83 The following certificates are used to authenticate the images.
196 the FIP along with the boot loader images. These certificates are loaded in
[all …]
A Dtrusted-board-boot-build.rst77 FIP will include the certificates corresponding to the selected Chain of
78 Trust. These certificates can also be found in the output build directory.
113 Both the FIP and FWU_FIP will include the certificates corresponding to the
114 selected Chain of Trust. These certificates can also be found in the output
A Dauth-framework.rst15 X.509v3 certificates to ferry Subject Public Keys, hashes and non-volatile
261 x509v3 certificates, signed ELF files or any other platform specific format).
376 PKI certificates (authentication images). It is expected that open source
640 The TBBR specifies the additional certificates that must accompany these images
645 identifiers for all the images and certificates that will be loaded during the
671 (i.e. the BL2 and Trusted Key certificates are signed with the ROT private
708 extracted from the certificates. In the case of the TBBR CoT, these parameters
/arm-trusted-firmware-2.8.0/docs/components/
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
72 non-root certificates which are authenticated using public-key
75 This property is not required for root-certificates
76 as root-certificates are validated using root of trust
84 This property is used by all certificates which are
330 which are currently specific to X.509 certificates for e.g. Object IDs.
A Dfirmware-update.rst177 authentication). Secure world certificates and non-AP images are examples
/arm-trusted-firmware-2.8.0/plat/nxp/common/fip_handler/fuse_fip/
A Dfuse.mk61 …$(error Error: Trusted Board Boot with X509 certificates not supported with FUSE_PROG build option)
/arm-trusted-firmware-2.8.0/docs/plat/nxp/
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
/arm-trusted-firmware-2.8.0/plat/socionext/synquacer/
A Dplatform.mk73 certificates: $(ROT_KEY)
/arm-trusted-firmware-2.8.0/plat/socionext/uniphier/
A Dplatform.mk107 certificates: $(ROT_KEY)
/arm-trusted-firmware-2.8.0/plat/nxp/common/tbbr/
A Dtbbr.mk132 certificates: $(ROT_KEY)
/arm-trusted-firmware-2.8.0/plat/imx/imx7/common/
A Dimx7.mk78 certificates: $(ROT_KEY)
/arm-trusted-firmware-2.8.0/docs/plat/arm/
A Darm-build-options.rst56 to sign the BL2 and Trusted Key certificates. Available options for
65 when creating the certificates.
70 ``ROT_KEY`` when creating the certificates.
/arm-trusted-firmware-2.8.0/plat/rpi/rpi3/
A Dplatform.mk211 certificates: $(ROT_KEY)
/arm-trusted-firmware-2.8.0/plat/imx/imx8m/imx8mp/
A Dplatform.mk128 certificates: $(ROT_KEY)
/arm-trusted-firmware-2.8.0/plat/hisilicon/hikey/
A Dplatform.mk154 certificates: $(ROT_KEY)
/arm-trusted-firmware-2.8.0/plat/hisilicon/hikey960/
A Dplatform.mk147 certificates: $(ROT_KEY)
/arm-trusted-firmware-2.8.0/plat/imx/imx8m/imx8mm/
A Dplatform.mk131 certificates: $(ROT_KEY)
/arm-trusted-firmware-2.8.0/plat/qemu/qemu/
A Dplatform.mk87 certificates: $(ROT_KEY)
/arm-trusted-firmware-2.8.0/docs/getting_started/
A Dbuild-options.rst543 tool to create certificates as per the Chain of Trust described in
545 include the certificates in the FIP and FWU_FIP. Default value is '0'.
549 the corresponding certificates, and to include those certificates in the
554 include the corresponding certificates. This FIP can be used to verify the
559 will not include the corresponding certificates, causing a boot failure.
866 and verify the certificates and images in a FIP, and BL1 includes support
868 of certificates in the FIP and FWU_FIP depends upon the value of the
/arm-trusted-firmware-2.8.0/docs/plat/
A Dwarp7.rst78 BL33=fiptool_images/u-boot.bin certificates all
/arm-trusted-firmware-2.8.0/
A DMakefile102 FIP_DEPS += certificates
1479 certificates: ${CRT_DEPS} ${CRTTOOL} target
/arm-trusted-firmware-2.8.0/docs/
A Dchange-log.md3306 - Added support for platform-defined certificates, keys, and extensions
3543 - Create only requested certificates
3652 certificates
3683 - Added support for platform certificates
5640 verification will also get faster because certificates are generated based on
6271 the PolarSSL SSL library to verify certificates and images. The OpenSSL
6272 library is used to create the X.509 certificates. Support has been added to
6273 `fip_create` tool to package the certificates in a FIP.

Completed in 32 milliseconds