Lines Matching refs:certificates

29 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
37 extensions. To sign the certificates, different signature schemes are available,
40 The certificates are categorised as "Key" and "Content" certificates. Key
41 certificates are used to verify public keys which have been used to sign content
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.
133 The SCP_BL2 and BL32 certificates are optional, but they must be present if the
195 On the host machine, a tool generates the certificates, which are included in
196 the FIP along with the boot loader images. These certificates are loaded in
219 and keys as inputs and generates the certificates (in DER format) required to
222 case they are not provided. The certificates are then passed as inputs to
225 The certificates are also stored individually in the output build directory.
228 library version to generate the X.509 certificates. The specific version of the