Abstract:
PROBLEM TO BE SOLVED: To solve the problem that conventional PCR bindings can yield very rigid protection of data, where any change to the software that executes on the system results in the inability to access the data. SOLUTION: This disclosure describes methods for using the TPM's configuration binding capabilities to lock data to a configuration in a manner that is flexible enough to allow the software in that configuration to be upgraded, under a trusted upgrade service, without causing the processing system to lose access to the data. Additionally, a processing system can provide for recovery of data when the processing system is no longer able to get into the predefined safe and approved configuration, e.g., recovery from a failed upgrade is allowed. COPYRIGHT: (C)2009,JPO&INPIT
Abstract:
A processing system with a trusted platform module (TPM) supports migration of digital keys. An application in the processing system creates a first configuration key 120 as a child of a TPM storage root key (SRK) 110 when the system has a first configuration. The application also creates an upgradeable root user key 130 associated with an upgrade authority as a child of the first configuration key. When the system has a second configuration, the application creates a second configuration key 122 as a child of the SRK and requests migration approval from the upgrade authority. In response to receiving approval from the upgrade authority, the application migrates the root user key 132 to be a child of the second configuration key. Compared to the conventional structure (fig. 2) the upgradeable key structure includes an extra layer (the configuration keys) in the hierarchy between the Root User Key 130 and the SRK.
Abstract:
A processing system with a trusted platform module (TPM) supports migration of digital keys. For instance, an application in the processing system may create a first configuration key as a child of a TPM storage root key (SRK) when the processing system has a first configuration. The application may also create an upgradable root user key associated with an upgrade authority as a child of the first configuration key. The application may also create a user key as a child of the upgradable root user key. When the processing system has a second configuration, the application may create a second configuration key as a child of the SRK. The application may request migration approval from the upgrade authority. In response to receiving the approval from the upgrade authority, the application may migrate the root user key to be a child of the second configuration key. Other embodiments are described and claimed.