Revocation of TPM Keys

  • Stefan Katzenbeisser
  • Klaus Kursawe
  • Frederic Stumpf
Conference paper

DOI: 10.1007/978-3-642-00587-9_8

Part of the Lecture Notes in Computer Science book series (LNCS, volume 5471)
Cite this paper as:
Katzenbeisser S., Kursawe K., Stumpf F. (2009) Revocation of TPM Keys. In: Chen L., Mitchell C.J., Martin A. (eds) Trusted Computing. Trust 2009. Lecture Notes in Computer Science, vol 5471. Springer, Berlin, Heidelberg


A Trusted Platform Module (TPM) offers a number of basic security services which can be used to build complex trusted applications. One of the main functionalities of a TPM is the provision of a protected storage, including access management for cryptographic keys. To allow for scalability in spite of the resource constraints of the TPM, keys are not stored inside the TPM, but in encrypted form on external, untrusted storage. This has the consequence that the actual key storage is not under control of the TPM, and it is therefore not possible to revoke individual keys. In this paper we introduce two basic methods to implement key revocation without major changes to the TPM command set, and without inhibiting backwards compatibility with the current specification. Our methods introduce no overhead for normal operation, and a reasonable small effort for managing revocable keys.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Copyright information

© Springer-Verlag Berlin Heidelberg 2009

Authors and Affiliations

  • Stefan Katzenbeisser
    • 1
  • Klaus Kursawe
    • 2
  • Frederic Stumpf
    • 3
  1. 1.Security Engineering GroupTechnische Universität DarmstadtDarmstadtGermany
  2. 2.Information and System Security GroupPhilips Research EuropeEindhovenThe Netherlands
  3. 3.Research Group IT-SecurityTechnische Universität DarmstadtDarmstadtGermany

Personalised recommendations