Cryptographic material sharing among entities with no direct trust relationship or connectivity
A mechanism to share cryptographic material across entities that may not have a direct trust relationship between or among each other, or no network connectivity, or some combination thereof, but where participating entities do share a trust relationship (or trusted connection(s)) with a common entity, sometimes referred to herein as a “conduit” entity. This technique enables such entities to leverage their trust relationship with a common “conduit” entity to share cryptographic material between or among themselves.
1. A method of sharing cryptographic material among a set of computing entities, wherein given computing entities do not share a direct trust relationship or network connectivity with one another, comprising:
at a conduit entity with which each of the set of computing entities shares a trusted communication path:
storing an indication that identifies a given one of the computing entities as a leader entity, wherein the cryptographic material to be shared is generated by the leader entity;
storing a value representing a synchronization state, the value having been generated by the leader entity applying a given function to the cryptographic material;
receiving a message from a computing entity that is not the leader entity and, in response, determining whether there is loss or corruption of the cryptographic material at the computing entity; and
when it is determined that there is loss or corruption of the cryptographic material at the computing entity, initiating a synchronization protocol among the computing entity, the conduit entity and the leader entity to auto-recover the cryptographic material from the leader entity to the computing entity via the conduit entity, the conduit entity being restricted from viewing the cryptographic material as the cryptographic material passes through to the computing entity.
2. The method as described in claim 1 wherein determining whether there is loss or corruption of the cryptographic material at the computing entity compares information in the message to the value.
3. The method as described in claim 1 wherein the synchronization protocol comprises:
receiving at the conduit entity a public key associated with the computing entity;
forwarding the public key associated with the computing entity to the leader entity;
receiving from the leader entity a result of the leader entity encrypting the cryptographic material with the public key associated with the computing entity; and
returning the result to the computing entity.
4. The method as described in claim 3 further including receiving a confirmation message from a target entity, the confirmation message having been generated at the target entity upon (i) the target entity's receipt of the result, and (ii) decrypting of the result using a private key to recover the cryptographic material, wherein the private key and the public key comprise an asymmetric key pair.
5. The method as described in claim 1 wherein the value is a cryptographic hash of the cryptographic material.
6. A computer program product comprising a non-transitory computer readable medium holding computer program instructions, the computer program instructions executed by a hardware processor on a conduit entity, the computer program instructions configured to facilitate sharing of cryptographic material among a set of computing entities by:
storing an indication that identifies a given one of the computing entities as a leader entity, wherein the cryptographic material to be shared is generated by the leader entity;
storing a value representing a synchronization state, the value having been generated by the leader entity applying a given function to the cryptographic material;
receiving a message from a computing entity that is not the leader entity and in response, determining whether there is loss or corruption of the cryptographic material at the computing entity; and
when it is determined that that there is loss or corruption of the cryptographic material at the computing entity, initiating a synchronization protocol among the computing entity, the conduit entity and the leader entity to auto-recover the cryptographic material from the leader entity to the computing entity via the conduit entity, the conduit entity being restricted from viewing the cryptographic material as the cryptographic material passes through to the computing entity;
wherein each of a set of computing entities shares a trusted communication path with the conduct entity that executes the synchronization protocol.
7. The computer program product as described in claim 6 wherein determining whether there is loss or corruption of the cryptographic material at the computing entity compares information in the message to the value.
8. The computer program product as described in claim 6 wherein the synchronization protocol comprises:
receiving at the conduit entity a public key associated with the computing entity;
forwarding the public key associated with the computing entity to the leader entity;
receiving from the leader entity a result of the leader entity encrypting the cryptographic material with the public key associated with the computing entity; and
returning the result to the computing entity.
9. The computer program product as described in claim 8 further including receiving a confirmation message from a target entity, the confirmation message having been generated at the target entity upon (i) the target entity's receipt of the result, and (ii) decrypting of the result using a private key to recover the cryptographic material, wherein the private key and the public key comprise an asymmetric key pair.
10. The computer program product as described in claim 6 wherein the value is a cryptographic hash of the cryptographic material.