credentials offered in step one and used in step two, and the issuing TPM. The remote attestation process is shown in figure \[fig:Remote\_Attestation\].

![Remote Attestation process.[]{data-label="fig:Remote_Attestation"}](Remote_Attestation.eps){width="40.00000%"}

Beside the attestation methods TC offers a concept to bind blobs of data to a single instantiation and state of a TPM. The `TPM_unbind` operation takes the data blob that is the result of a `Tspi_Data_Bind` command and decrypts it for export to the user. The caller must authorise the use of the key that will decrypt the incoming blob. In consequence this data blob is only accessible if the platform is in the namely state which is associated with the respective PCR value.

A mobile version of the TPM is currently being defined by the TCG’s Mobile Phone Working Group [@MTM09]. This so-called Mobile Trusted Module (MTM) differs significantly from the TPM of the PC world and is in fact more powerful in some respects. In particular, it contains a built-in verifier for attestation requests, substituting partly for an external PCA. Both TPM and MTM are a solid basis for application architectures and scenarios. Trusted Computing not only affects the world of networked PCs but will also heavily impact the mobile industry. Accordingly, 