Crypto tunnelling between two-way trusted network devices in a secure peer-to-peer data network

1. A method comprising:

generating, by a secure executable container executed by an endpoint device in a secure peer-to-peer data network, a secure private key and a corresponding first secure public key;

first establishing, by the secure executable container, a corresponding two-way trusted relationship with a second endpoint device, including receiving a second secure public key of the second endpoint device;

second establishing, by the secure executable container, a corresponding two-way trusted relationship with a replicator device, including receiving a third secure public key of the replicator device;

generating, by the secure executable container using the second secure public key, a secure data packet destined for the second endpoint device, including generating an encrypted payload for the secure data packet;

generating, by the secure executable container using the third secure public key of the replicator device, a secure tunneled data packet based on encrypting the secure data packet for the secure tunneled data packet; and

outputting to the replicator device, by the secure executable container, the secure tunneled data packet.

2. The method of claim 1 , further comprising preventing, by the secure executable container, any executable resource in the endpoint device from accessing the secure peer-to-peer data network, accessing any unencrypted form of any first secure data structure stored in the endpoint device, or accessing any second secure data structure generated for secure communications in the secure peer-to-peer data network, without authorized access via a prescribed Application Programming Interface (API) required by the secure executable container.

3. The method of claim 1 , wherein:

the second establishing includes receiving, by the secure executable container from a management device in the secure peer-to-peer data network, the third secure public key during secure registration of the endpoint device in in the secure peer-to-peer data network;

the first establishing includes receiving, by the secure executable container, the second secure public key according to a prescribed secure salutation protocol.

4. The method of claim 1 , wherein:

the generating of the secure data packet includes digitally signing at least a portion of the secure data packet with the secure private key;

the generation of the secure tunneled data packet includes digitally signing at least the encrypting of the secure data packet with the secure private key.

5. The method of claim 4 , wherein:

the generating of the secure data packet comprises generating a first temporal key, encrypting the first temporal key into a first encrypted temporal key using the second secure public key, and adding the first encrypted temporal key to the secure data packet; and

the generating of the secure tunneled data packet comprises generating a second temporal key, encrypting the second temporal key into a second encrypted temporal key using the third secure public key, and adding the second encrypted temporal key to the secure tunneled data packet.

6. The method of claim 5 , wherein:

the generating an encrypted payload for the secure data packet comprises encrypting a payload using one of the second secure public key or the first temporal key;

the encrypting the secure data packet for the secure tunneled data packet comprises encrypting the secure data packet using one of the third secure public key or the second temporal key.

7. One or more non-transitory tangible media encoded with logic for execution by a machine and when executed by the machine operable for:

generating, by the one or more non-transitory tangible media implemented as a secure executable container executed by the machine implemented as an endpoint device in a secure peer-to-peer data network, a secure private key and a corresponding first secure public key;

first establishing, by the secure executable container, a corresponding two-way trusted relationship with a second endpoint device, including receiving a second secure public key of the second endpoint device;

second establishing, by the secure executable container, a corresponding two-way trusted relationship with a replicator device, including receiving a third secure public key of the replicator device;

generating, by the secure executable container using the second secure public key, a secure data packet destined for the second endpoint device, including generating an encrypted payload for the secure data packet;

generating, by the secure executable container using the third secure public key of the replicator device, a secure tunneled data packet based on encrypting the secure data packet for the secure tunneled data packet; and

outputting to the replicator device, by the secure executable container, the secure tunneled data packet.

8. The one or more non-transitory tangible media of claim 7 , further operable for preventing, by the secure executable container, any executable resource in the endpoint device from accessing the secure peer-to-peer data network, accessing any unencrypted form of any first secure data structure stored in the endpoint device, or accessing any second secure data structure generated for secure communications in the secure peer-to-peer data network, without authorized access via a prescribed Application Programming Interface (API) required by the secure executable container.

9. An apparatus implemented as a physical machine, the apparatus comprising:

non-transitory machine readable media configured for storing executable machine readable code implemented as a secure executable container;

a device interface circuit; and

a processor circuit configured for executing the machine readable code, and when executing the machine readable code operable for:

generating, by the secure executable container, a secure private key and a corresponding first secure public key, the apparatus implemented as an endpoint device in a secure peer-to-peer data network,

first establishing, by the secure executable container, a corresponding two-way trusted relationship with a second endpoint device, including receiving a second secure public key of the second endpoint device,

second establishing, by the secure executable container, a corresponding two-way trusted relationship with a replicator device, including receiving a third secure public key of the replicator device,

generating, by the secure executable container using the second secure public key, a secure data packet destined for the second endpoint device, including generating an encrypted payload for the secure data packet,

generating, by the secure executable container using the third secure public key of the replicator device, a secure tunneled data packet based on encrypting the secure data packet for the secure tunneled data packet, and

outputting to the replicator device, by the secure executable container, the secure tunneled data packet.

10. The apparatus of claim 9 , wherein the secure executable container is configured for preventing any executable resource in the endpoint device from accessing the secure peer-to-peer data network, accessing any unencrypted form of any first secure data structure stored in the endpoint device, or accessing any second secure data structure generated for secure communications in the secure peer-to-peer data network, without authorized access via a prescribed Application Programming Interface (API) required by the secure executable container.