Anzeige
Erschienen in:
2014 | OriginalPaper | Buchkapitel
8. Managing TPM2
verfasst von : Graeme Proudler, Liqun Chen, Chris Dalton
Erschienen in: Trusted Computing Platforms
Aktivieren Sie unsere intelligente Suche, um passende Fachinhalte oder Patente zu finden.
Wählen Sie Textabschnitte aus um mit Künstlicher Intelligenz passenden Patente zu finden. powered by
Markieren Sie Textabschnitte, um KI-gestützt weitere passende Inhalte zu finden. powered by
Abstract
TPM2 must be managed before it can perform useful work. First of all, management software must learn a particular TPM2’s properties, such as the cryptographic algorithms that it supports, what TPM commands it supports, and what TPM resources are available. A TPM2’s Protected Storage hierarchies require the most management effort because TPMs typically can’t store many keys, data, and authorisation sessions at one time. Management software must keep swapping keys, data, and sessions in and out of the TPM. Short-term caches don’t require a caller to keep providing authorisation, but long-term caches do. Management software must also manage the TPM’s response to dictionary attacks, manage any TPM audit that is required, and align the TPM’s clock to UTC.