a limited validity period ore be used a specified number of times.

For the adept, some base concepts of Trusted Computing (TC) look very similar to Identity Management (IDM). We exploit the analogy between TC and IDM and construct a ticket system using TC functionality, thus obtaining a cornerstone of IDM systems. The applicability of such a *trusted ticket system* is shown in the context of a reputation system and a push service.

Section \[sec:TCess\] provides necessary background on TC. Section \[sec:TC-Tickets\], developing the trusted ticket system proper is subdivided in \[sec:AIKTickets\], explaining how to use Attestation Identity Keys (AIKs) for the realisation of tickets, and \[sec:AcqRed\] detailing the proceedings for the acquisition and redemption of the latter. Section \[sec:GenArc\] outlines a general service access architecture utilising trusted tickets, with a high degree of separation of duties, providing for pseudonymity, accountability, and charging functionality. Section \[sec:App\] embeds trusted ticket systems in the two mentioned application contexts and discusses resulting benefits. Conclusions are drawn in Section \[sec:conclusions\].

Trusted Computing Essentials {#sec:TCess}
============================

Trusted computing uses a hardware anchor as a root of trust and is now entering the mobile domain with the aim to provide a standardised security infrastructure. Trust in 