-
Notifications
You must be signed in to change notification settings - Fork 3
Encrypted Messages
amitshah edited this page Apr 21, 2018
·
2 revisions
Referencing SJCLs ECC elgamal based asymmetric encryption/decryption.
When opening a channel, an end user generates a new encryption key. You can submit an elgamal public key (bytes) and your channel partner will encrypt all messages with this key.
Alternative is to queue up a publicKey transfer message at the very beginning of any messaging interaction.
To allow for intermittent network connectivity between channel partners, one can simply queue the encrypted messages for delivery. In this way we overcome the highly variable connectivity of mobile clients.