Resources
Identity Use Cases & Scenarios.- FIDIS Deliverables.
- Identity of Identity.
- Interoperability.
- Profiling.
- Forensic Implications.
- HighTechID.
- D3.1: Overview on IMS.
- D3.2: A study on PKI and biometrics.
- D3.3: Study on Mobile Identity Management.
- D3.5: Workshop on ID-Documents.
- D3.6: Study on ID Documents.
- D3.7: A Structured Collection on RFID Literature.
- D3.8: Study on protocols with respect to identity and identification – an insight on network protocols and privacy-aware communication.
- D3.9: Study on the Impact of Trusted Computing on Identity and Identity Management.
- D3.10: Biometrics in identity management.
- D3.11: Report on the Maintenance of the IMS Database.
- D3.15: Report on the Maintenance of the ISM Database.
- D3.17: Identity Management Systems – recent developments.
- D12.1: Integrated Workshop on Emerging AmI Technologies.
- D12.2: Study on Emerging AmI Technologies.
- D12.3: A Holistic Privacy Framework for RFID Applications.
- D12.4: Integrated Workshop on Emerging AmI.
- D12.5: Use cases and scenarios of emerging technologies.
- D12.6: A Study on ICT Implants.
- D12.7: Identity-related Crime in Europe – Big Problem or Big Hype?.
- D12.10: Normality Mining: Results from a Tracking Study.
- Privacy and legal-social content.
- Mobility and Identity.
- Other.
- IDIS Journal.
- FIDIS Interactive.
- Press & Events.
- In-House Journal.
- Booklets
- Identity in a Networked World.
- Identity R/Evolution.
D3.9: Study on the Impact of Trusted Computing on Identity and Identity Management
 |
Title: TCG SOFTWARE STACK (TSS) SPECIFICATION OVERVIEW |
 |
TCG Software Stack (TSS) Specification Overview
The TCG Software Stack (TSS) provides a platform independent software interface for accessing TPM functions [98]. The TSS enables the creation of interfaces for existing cryptographic APIs like MS-CAPI or PKCS#11. This enables TPM support for current and future applications that are using those APIs. In order to take full advantage of a TPM’s attestation functions, however, applications will have to support TSS directly.
TSS defines three software interfaces for TCG-enabled software. An overview on these interfaces and some possibilities to make use of them is given in figure 6.
The kernel mode TPM device driver is documented in the TCG TPM Specification. Above the kernel mode driver, a user mode driver, called TPM Device Driver Library (TDDL), provides an operating system independent interface for TPM applications. This separation should ensure that different implementations of TSS are able to communicate with any TPM device and enable the implementation of TPM software emulators as user mode components.
The TSS Core Services (TCS) offers an interface to a common set of platform services like TCG Service Providers or RPC services for communication to a remote TCG Service Provider. The TCS is run as a system process in user mode. It provides services for credential and key management, measurement and event management to handle event log entries and access to PCRs. Additionally it manages access to the TPM device itself since there might run multiple TCG Service Providers in parallel on a single platform.
The TCS must be trusted to manage authorization information which is supplied to the TPM.
Fig5: TCG Software Stack (TSS) and Interaction Scenarios
The TCG Service Provider (TSP) provides an interface for the C programming language. This interface can be used by applications that make use of TPM features. TSPs provide context management which allows efficient use of application and TSP resources and basic cryptographic functions like the computation of message digests and signature generation. Other cryptographic service providers may use the TSP Interface (TSPI) to communicate with the TPM device. This enables applications not supporting TSP to use TPM functions through their currently supported cryptographic API.
| |
   |
|
| 10 / 38 |
