Lines Matching refs:verify

14    terms of certificate hierarchy and the mechanisms used to verify a
23    -  The mechanism used to verify the transported information i.e. the
74 behind them. These aspects are key to verify a Chain of Trust.
139 performed to verify it:
188 #. Export functions to verify an image which uses an authentication method that
210    Key Certificate in the TBBR-Client spec. contains information to verify
215 #. Reusing memory meant for a data image to verify authentication images e.g.
221    never exceed the size of a data image. It should be possible to verify this
358 verified. Each image has a set of properties which allow the AM to verify it.
437 be used to verify either the current or the next image in the CoT sequence.
446 which will be used to verify it. As described in the Section "Authentication
467 #. Extract authentication parameters from a parent image in order to verify a
468    child image e.g. to verify the certificate image, the public key has to be
483 required to verify an image.
502 verify the image.
546 A parameter described by ``auth_param_type_desc_t`` to verify an image could be
571 parameters that should be extracted from it and used to verify the next image
594    section. These are used to verify the current image.
596 #. Parameters which are used to verify the next image in the current CoT. These
908 i.e. verify a hash or a digital signature. ARM platforms will use a library