sergiodt
/
vn-verdnaturachat
0
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
vn-verdnaturachat/app/lib/encryption
History
Gleidson Daniel Silva 4172d563b7
Chore: Server API types POC - loadMessagesForRoom (#3765) 
* create interface and implements base types

* fix some types

* Update app/lib/methods/updateMessages.ts

Co-authored-by: Diego Mello <diegolmello@gmail.com>

* fix date type

* apply types changes

* fix type

* fix date value

* fix types

* typescript things...

Co-authored-by: Diego Mello <diegolmello@gmail.com>
 		2022-02-25 18:32:03 -03:00
..
README.md [NEW] E2E Encryption (#2394) 2020-09-11 11:31:38 -03:00
constants.ts Chore: Migrate lib/encryption folder to TypeScript (#3639) 2022-02-16 17:14:28 -04:00
encryption.ts Chore: Server API types POC - loadMessagesForRoom (#3765) 2022-02-25 18:32:03 -03:00
index.ts Chore: Migrate lib/encryption folder to TypeScript (#3639) 2022-02-16 17:14:28 -04:00
room.ts Chore: Migrate lib/encryption folder to TypeScript (#3639) 2022-02-16 17:14:28 -04:00
utils.ts Chore: Migrate lib/encryption folder to TypeScript (#3639) 2022-02-16 17:14:28 -04:00

README.md

Rocket.Chat Mobile

E2E Encryption

Note: This feature is currently in beta. Uploads will not be encrypted in this version. You can check this documentation for further information about the web client.

How it works

  • Each user has a public and private key (asymmetric cryptography).
  • The user private key is stored encrypted on the server and it can be decrypted on clients only using the user E2E encryption password.
  • A room key is generated using the public key of each room member (symmetric cryptography).
  • Users can decrypt the room key using their private key.
  • Each room has a unique identifier which make users able to request a room key.
  • The room unique identifier is called e2eKeyId and it's a property of the room collection.
  • The room key is called E2EKey and it's a property of the subscription collection.
  • After the room key is decrypted, the user is able to encrypt and decrypt messages of the room.

User keys

  • If the user doesn't have keys neither locally nor on the server, we create and encrypt them using a random password. These encrypted keys are sent to the server (so other clients can fetch) and saved locally.
  • If the user have keys stored on server, but doesn't have them stored locally, we fetch them from the server and request a password to decrypt the keys.

Room keys

  • If the room has a E2EKey, we decrypt it using the user key.
  • If the room doesn't have a E2EKey, but has a e2eKeyId, we emit an event on stream-notify-room-users sending the roomId and the e2eKeyId requesting the E2EKey from any online room member.
  • If the room have none of them, we create new ones and send them back to the server.