End to End encryption

[midget3111]

Also very far down the road. Will require an overhaul.

[trigg]

E2E proposition:

This is currently some abstract musings on how we could manage this. I just want somewhere to put the ideas and this seems the best place.

Each new client connection (not just user but each device) will need to generate an asymmetric key and a UUID. It will store the private key locally and securely (discuss : what is secure enough?)

The public key should be sent to server with the UUID, and kept in a collection of 'devices owned by user', probably as a new table

Whenever a client is sent a user list, it must include a collection of known device pubkey&UUID per user. Alternatively, the list could be ascribed to text room updates and thus anonymising which pubkey is which real user.

Any messages sent to chat rooms will need to be encoded for each user+device pair and sent to store on server. The message MUST also be encrypted for the sending user for all devices as otherwise they'll not see their own messages. This will result in probably hundreds of rows per single message. (discuss: probably need to have some auto-delete option for servers to remove old messages, as otherwise slightly busy systems will get bogged down in data storage)

When requesting messages for a room, clients must send their Device UUID to collect all the messages in encrypted format, and locally decrypt them to display.

Currently there is no direct-message facility, simply because the lack of E2E messaging made it impossible to promise any kind of privacy. This feature could be considered After e2e is proven for text rooms.