Lines Matching refs:from
158 Authentication module to authenticate it, following the CoT from ROT to Image.
214 will have been extracted from the parent image i.e. BL31 content
264 image. The IPM obtains the image format from the CoT and calls the right IPL to
283 parameters should be obtained from the parent image using the IPM.
431 extract the data corresponding to that parameter from an image. This data will
457 parameter should be extracted from an image.
462 #. Extract authentication parameters from a parent image in order to verify a
464 obtained from the parent image.
489 from an image. For example, the hash of a BL3x image in its corresponding
542 obtained from either the image itself or its parent image. The memory allocated
544 parameters which are obtained from the parent for verifying a child image need
561 For parameters that can be obtained from the child image itself, the IPM is
566 parameters that should be extracted from it and used to verify the next image
593 from the current image once it has been verified.
647 these identifiers can be obtained from ``include/common/tbbr/tbbr_img_def.h``.
670 is NULL, the authentication parameters will be obtained from the platform
677 will point to specific information required to extract that parameter from
685 from the parent image. The following parameter descriptors must be
688 - ``data``: data to be hashed (obtained from current image)
689 - ``hash``: reference hash (obtained from parent image)
692 the private key whose public part is extracted from the parent image (or
696 - ``pk``: the public key (obtained from parent image)
697 - ``sig``: the digital signature (obtained from current image)
698 - ``alg``: the signature algorithm used (obtained from current image)
699 - ``data``: the data to be signed (obtained from current image)
702 parameters must be extracted from an image once it has been authenticated.
708 extracted from the certificates. In the case of the TBBR CoT, these parameters
714 be used to extract the parameter data from the corresponding image.
859 is used to extract a public key from the parent image. If the cookie is an
860 OID, the key is extracted from the corresponding x509v3 extension. If the
862 the parent image is NULL, the public key is obtained from the platform
865 the signature from the certificate.
867 extract the signature algorithm from the certificate.
869 to extract the data to be signed from the certificate.
872 Trusted World public key needs to be extracted from the certificate. A new entry
876 descriptor is used to extract the public key from an x509v3 extension with OID
882 using the Trusted World public key obtained previously from the Trusted Key
890 using the BL31 public key obtained previously from the BL31 Key certificate.
897 with the hash obtained from the BL31 certificate. The image descriptor contains