secure communication

[muhamadazmy]

Current version of rmb communicate between rmb instances over http. While the message integrity and authenticity is granted by the means of digital signature. The message content itself is still in plain-text. Which means a man in the middle attack can simply read the message content which can expose secrets (imagine setting passwords in env variables that are sent during container creation)

This can be solved in one in many means:

• Use HTTPS instead of HTTP (using self signed certificate?) self signed certificate is not secure this can be still be intercepted (again with man in the middle attack) also can be manipulated but then the signature will show that the message has been modified.
• Encrypting the data with the remote twin public key. This is probably the better approach. It means the owner of the secure key is the only one who can decrypt the message.

The problem with both approaches is that they are both not backward compatible.