Cryptographic key update management method and apparatus

• US 8,045,713 B2
• Filed: 03/30/2004
• Issued: 10/25/2011
• Est. Priority Date: 04/08/2003
• Status: Expired due to Fees

• Current Assignee: Micro Focus LLC (Open Text Corporation)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Lain, Antonio, Borisov, Viacheslav
• Primary Examiner(s): Flynn; Nathan
• Assistant Examiner(s): WRIGHT, BRYAN F
• Application Number:
  US10/814,608
• Publication Number:
  US 20050018853A1
• Time in Patent Office: 2,765 Days
• Field of Search: 380/278
• US Class Current: 380/277
• CPC Class Codes: H04L 2209/60 Digital content management, e.g. content distribution
• CPC Class Codes: H04L 63/064 Hierarchical key distribution, e.g. by multi-tier trusted parties
• CPC Class Codes: H04L 63/065 for group communications cryptographic mechanisms or cryptographic arrangements for key management involving conference or group key H04L9/0833
• CPC Class Codes: H04L 9/0836 using tree structure or hierarchical structure
• CPC Class Codes: H04L 9/0891 Revocation or update of secret information, e.g. encryption key update or rekeying

Abstract

A method and apparatus is provided for consolidating cryptographic key updates, the consolidated update information enabling, for example, a returning member of a secure group who has been offline, to recover the current group key, at least in most cases. The unconsolidated key updates each comprise an encrypted key, corresponding to a node of a key hierarchy, that has been encrypted using a key which is a descendant of that node. The key updates are used to maintain a key tree with nodes in this tree corresponding to nodes in the key hierarchy. Each node of the key tree is used to store, for each encrypting key used in respect of the encrypted key associated with the node, the most up-to-date version of the encrypted key with any earlier versions being discarded. The key tree, or a subset of the tree, is then provided to group members.

Claims

1. Apparatus for managing key updates in a logical key hierarchy, comprising:

a communication interface operable for receiving at a cache, records generated by a key-hierarchy manager for members using the logical key hierarchy, wherein the records include key updates comprising an encrypted key corresponding to a node of the logical key hierarchy and encrypted using a key that corresponds to a descendant of that node, hierarchy-node information for both the encrypted and encrypting keys and key-version information for at least the encrypted key; and

a manager of the cache operable to consolidate the records into a key history tree, wherein the key history tree has the same structure as the logical key hierarchy, the manager storing at each node of the key history tree, for each encrypted key associated with the node, the most up-to-date version of the encrypted key and its version information with any earlier versions being discarded.

2. Apparatus according to claim 1, wherein the manager is arranged to store each said most up-to-date version of a said encrypted key by storing the record containing the latter, with any previously-stored record being superseded is discarded.

3. Apparatus according to claim 1, wherein the manager is arranged to store in association with each tree node, along with the most up-to-date version of the corresponding encrypted key stored for each encrypting key used in respect of that encrypted key, version information for the encrypting key used to encrypt said most up-to-date version of the encrypted key, this version information being included in the record providing said most up-to-date version of the encrypted key.

4. Apparatus according to claim 3, wherein the manager is arranged to replace the version of the encrypted key stored in association with a tree node for a particular encrypting key, with any subsequently received later version of the encrypted key provided the latter has been encrypted with a version of the encrypting key that is the same or later than the version used for encrypting the existing stored encrypted key.

5. Apparatus according to claim 1, further comprising a working-set generator for processing the key history tree to generate a subset of the key history tree enabling, at least within a target failure rate, all clients associated with the key hierarchy to recover the current root key of the latter.

6. Apparatus according to claim 5, wherein the working set generator comprises control means for receiving feedback on the current root-key recovery failure rate and for controlling the size of said subset to approach the actual failure rate to said target failure rate.

7. Apparatus according to claim 6, wherein the working set generator further comprises determining means for determining the likelihood of a tree node being required to enable recovery the current root key relative to at least one of the age of the node, or of an encrypted key associated with the node, and an estimate of the number of possible clients that will need the node.

8. Apparatus according to claim 1, wherein the manager is arranged to maintain said key history tree only in respect of keys corresponding to the nodes of a predetermined sub-hierarchy of said hierarchy and keys for the path from the head of this sub-hierarchy that terminates at the root of the hierarchy.

9. Apparatus according to claim 1, further comprising a key-hierarchy manager for managing said key hierarchy in dependence on the addition or removal of members, the key-hierarchy manager being arranged to output said records both to currently available members and to said apparatus as notification of the changes made by the key-hierarchy manager to the key hierarchy, said apparatus being arranged to provide said key history tree, or a subset of said key history tree, to members who subsequently become available as a consolidated notification of the changes made by the key-hierarchy manager to the key hierarchy to enable said members to recover the current root key of the key hierarchy at least within a target failure margin.

10. Apparatus according to claim 1, further comprising a key-hierarchy manager for managing said key hierarchy in dependence on the addition or removal of members, the key-hierarchy manager being arranged to output said records to said apparatus, said apparatus being arranged to provide said key history tree, or a subset of said key history tree, to members as a consolidated notification of the changes made by the key-hierarchy manager to the key hierarchy to enable said members to recover the current root key of the key hierarchy at least within a target failure margin.

11. Apparatus according to claim 10, wherein the apparatus including the key-hierarchy manager forms part of an anonymous group content distribution arrangement;

the key history tree, or a subset of key history tree, being sent to members in association with content encrypted with a key that is one of;

the key-hierarchy root key, and

a key encrypted using the key-hierarchy root key and provided in encrypted form along with the encrypted content.

12. A system comprising multiple apparatuses and a key-hierarchy manager for managing said key hierarchy in dependence on the addition or removal of members and for outputting key update records reflecting changes made to the key hierarchy;

the apparatuses being configured in a multiple-level hierarchical arrangement comprising a first-level apparatus arranged to receive the records output by the key-hierarchy manager, and one or more lower levels of apparatuses each arranged to receive the key history tree, or a subset of key history tree, produced by a said apparatus at the next level up, the apparatuses at the lowest level of the hierarchical arrangement each being arranged to provide its key history tree, or a subset of its key history tree, to a respective sub-group of members;

the apparatuses at each level of said hierarchical arrangement, other than said first level, each being arranged to maintain its said key history tree only in respect of keys corresponding to the nodes of a respective predetermined sub-hierarchy of said key hierarchy and keys for the path from the head of this sub-hierarchy that terminates at the root of the key hierarchy.

13. A method of consolidating key updates provided in records that a key-hierarchy manager generates for members using a key-hierarchy, each comprising an encrypted key corresponding to a node of the key hierarchy that is used by the members and encrypted using a key that corresponds to a descendant of that node, hierarchy-node information for both the encrypted and encrypting keys, and key-version information for at least the encrypted key;

the method comprising a tree-maintenance step of maintaining in a computer, on the basis of said records, a key history tree with tree nodes corresponding to nodes in said key hierarchy, this tree-maintenance step comprising a sub-step of storing in association with each tree node of the key history tree, for each encrypting key used in respect of the encrypted key associated with the node, the most up-to-date version of the encrypted key and its version information with any earlier versions being discarded.

14. A method according to claim 13, wherein in said sub-step each, said most up-to-date version of a said encrypted key is stored by storing the record containing the latter, with any previously-stored record being superseded is discarded.

15. A method according to claim 13, wherein in said sub-step, the version information of the encrypting key used to encrypt said most up-to-date version of the encrypted key is stored with the latter.

16. A method according to claim 13, wherein in said sub-step, the version of the encrypted key stored in association with a tree node for a particular encrypting key, is replaced with any subsequently received later version of the encrypted key provided the latter has been encrypted with a version of the encrypting key that is the same or later than the version used for encrypting the existing stored encrypted key.

17. A method according to claim 13, further comprising the further step of processing the key history tree to generate a subset of the key history tree enabling, at least within a target failure rate, all clients associated with the key hierarchy to recover the current root key of the key hierarchy.

18. A method according to claim 17, wherein the further step comprises receiving feedback on the current root-key recovery failure rate and controlling the size of said subset to approach the actual failure rate to said target failure rate.

19. A method according to claim 18, wherein said further step further comprises determining the likelihood of a tree node being required to enable recovery of the current root key, this determination being based on at least one of the age of the node, or of an encrypted key associated with the node, and an estimate of the number of possible clients that will need the node.

20. A method according to claim 13, wherein said key history tree is maintained only in respect of keys corresponding to the nodes of a predetermined sub-hierarchy of said key hierarchy and keys for the path from the head of this sub-hierarchy that terminates at the root of the key hierarchy.

21. A method of providing key updates to members using the key hierarchy according to claim 13, comprising the steps of:

managing the key hierarchy in dependence on the addition or removal of members and outputting, as notification of the changes made to the key hierarchy, records that each comprise an encrypted key corresponding to a node of the key hierarchy and encrypted using a key which is a descendant of that node, and hierarchy-node and key-version information for both the encrypted and encrypting keys; and

consolidating said records and providing said key history tree, or a subset of said key history tree, to members enabling these members to recover the current root key of the key hierarchy at least within a target failure margin.