Lines Matching refs:service
20 a firmware TPM (fTPM) service implemented on top of OP-TEE.
25 party (f)TPM service and they try to be as general as possible. Different
28 (or even a different type of service to provide the attestation)
40 contain a third party fTPM service which in turn will be used to process the
44 for convenience. As the fTPM service used is an OP-TEE TA, it was easy to add
50 - **OP-TEE**: As stated earlier, the fTPM service used in this PoC is built as an
59 - **fTPM Service**: We use a third party fTPM service in order to validate
60 the Measured Boot functionality. The chosen fTPM service is a sample
62 reference implementation from Microsoft. The service was updated in order
68 Arm does not provide an fTPM implementation. The fTPM service used here
70 service as provided by TF-A. As such, it is beyond the scope of this
72 fTPM service.
74 - **TPM Kernel module**: In order to interact with the fTPM service, we need
78 fTPM service. We use this in order to read the PCRs with the measurements.
84 extensions to enable Measured Boot and an fTPM service. Therefore, we can rely
176 (2) calls ``tpm2_pcrread``, which will access the fTPM service to read the
188 The secure world terminal should show the debug logs for the fTPM service,
472 The fTPM service used has support only for 16 PCRs, therefore the content
485 service. The build options for this service are tailored for the PoC and defined in