Searched refs:certificates (Results 1 – 14 of 14) sorted by relevance
/device/linaro/bootloader/arm-trusted-firmware/docs/ |
D | trusted-board-boot.rst | 32 The remaining components in the CoT are either certificates or boot loader 33 images. The certificates follow the `X.509 v3`_ standard. This standard 34 enables adding custom extensions to the certificates, which are used to store 37 In the TBB CoT all certificates are self-signed. There is no need for a 40 extensions. To sign the certificates, the PKCS#1 SHA-256 with RSA Encryption 44 The certificates are categorised as "Key" and "Content" certificates. Key 45 certificates are used to verify public keys which have been used to sign content 46 certificates. Content certificates are used to store the hash of a boot loader 50 non-standard extension fields in the `X.509 v3`_ certificates. 61 The private part is used to sign the key certificates corresponding to the [all …]
|
D | auth-framework.rst | 20 X.509v3 certificates to ferry Subject Public Keys, hashes and non-volatile 266 x509v3 certificates, signed ELF files or any other platform specific format). 381 PKI certificates (authentication images). It is expected that open source 643 The TBBR specifies the additional certificates that must accompany these images 648 identifiers for all the images and certificates that will be loaded during the 674 (i.e. the BL2 and Trusted Key certificates are signed with the ROT private 709 extracted from the certificates. In the case of the TBBR CoT, these parameters
|
D | user-guide.rst | 371 tool to create certificates as per the Chain of Trust described in 373 include the certificates in the FIP and FWU\_FIP. Default value is '0'. 377 the corresponding certificates, and to include those certificates in the 382 include the corresponding certificates. This FIP can be used to verify the 387 will not include the corresponding certificates, causing a boot failure. 559 and verify the certificates and images in a FIP, and BL1 includes support 561 of certificates in the FIP and FWU\_FIP depends upon the value of the 648 to sign the BL2 and Trusted Key certificates. Available options for 658 creating the certificates. 663 when creating the certificates. [all …]
|
D | firmware-update.rst | 88 authentication). Secure world certificates and non-AP images are examples
|
D | change-log.rst | 681 BL2 use the PolarSSL SSL library to verify certificates and images. The 682 OpenSSL library is used to create the X.509 certificates. Support has been 683 added to ``fip_create`` tool to package the certificates in a FIP.
|
D | firmware-design.rst | 1573 images (e.g. certificates) or firmware images prior to being transfered to its
|
/device/linaro/bootloader/edk2/BaseTools/Source/Python/Pkcs7Sign/ |
D | Readme.md | 3 …nds, and user MUST set a UNIQUE Subject Name ("Common Name") on these three different certificates. 13 When a user uses OpenSSL (req or ca command) to generate the certificates, OpenSSL will use the ope…
|
/device/linaro/bootloader/arm-trusted-firmware/plat/socionext/uniphier/ |
D | platform.mk | 103 certificates: $(ROT_KEY)
|
/device/linaro/bootloader/arm-trusted-firmware/plat/qemu/ |
D | platform.mk | 73 certificates: $(ROT_KEY)
|
/device/linaro/bootloader/arm-trusted-firmware/ |
D | Makefile | 107 FIP_DEPS += certificates 635 certificates: ${CRT_DEPS} ${CRTTOOL} target
|
/device/google/cuttlefish_vmm/aarch64-linux-gnu/ |
D | builder-packages.txt | 19 ca-certificates 20190110
|
/device/google/cuttlefish_vmm/x86_64-linux-gnu/ |
D | builder-packages.txt | 20 ca-certificates 20190110
|
/device/linaro/bootloader/edk2/SecurityPkg/ |
D | SecurityPkg.dec | 121 …## GUID used to "certdb"/"certdbv" variable to store the signer's certificates for common variable…
|
/device/linaro/bootloader/edk2/CryptoPkg/Library/OpensslLib/ |
D | EDKII_openssl-1.0.2j.patch | 1347 - fprintf(stderr, "unable to load certificates: %s\n", file); 1646 +of certificates and CRLs against the current time. If X509_VERIFY_PARAM_set_time()
|