Feature: optional encryption in dmsg (similar to http/https)

[ayuryshev]

Feature description

Configurable optional encryption of packets similar to optional encryption in http/https.

Is your feature request related to a problem? Please describe.

Switching off encryption is supposed mostly for debugging and diagnostic purposes (similar as usage of http today).

Always turned on encryption:

• complicates network diagnostics (similar to https) - it's impossible to discern packets by content, it's possible to only guess by size
• noise encryption could be very CPU-hungry - depending on (un)availability of cryptography extensions of particular CPU it could eat most/substantial of CPU time. That makes CPU profiling more hard, it could conceal existing problems of other parts of code.

Describe the solution you'd like

1. Options that allows to Dial encrypted/non-encrypted communication
2. Options that allows to Accept encrypted/non-encrypted communication

Describe alternatives you've considered

Additional context

Possible implementation

• Extend options of dmsg.Client so that it Dial with encrypted/nonecrypted start of communication
• Implement noise-less communication without Encrypt/Decrypt
• Change Accept so that it can discern cases of encrypted/nonencrypted communications