89e0a40d95
* create index file * remove roomTypeToApiType from rocketchat and fix imports * move TOKEN_KEY to const file * move CURRENT_SERVER to const file * move CERTIFICATE_KEY to const file * getRoom * rename getSlashCommands * getSlashCommands * readMessages * getRooms * loadThreadMessages * loadNextMessages * loadSurroundingMessages * loadMessagesForRoom * loadMissedMessages * clearCache * canOpenRoom * setUser * userPreferencesMethods * getCustomEmojis * callJtisi * triggerActions * getPermissions * getRoles * getSettings * getUsersPresence * logout * sendFileMessage * shareExtension * sendMessage * enterpriseModules * getPermalinks * search * change RocketChat.metodo to direct call * fix types * Fix login * Fix createChannel * migrate service methods to Service.method call * change call directly to RocketChat because the use of this * rollback * rollback * fix create discussion * fix import Co-authored-by: Diego Mello <diegolmello@gmail.com> |
||
|---|---|---|
| .. | ||
| README.md | ||
| encryption.ts | ||
| index.ts | ||
| room.ts | ||
| utils.ts | ||
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
e2eKeyIdand it's a property of theroomcollection. - The room key is called
E2EKeyand it's a property of thesubscriptioncollection. - 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 ae2eKeyId, we emit an event on stream-notify-room-users sending theroomIdand thee2eKeyIdrequesting theE2EKeyfrom any online room member. - If the room have none of them, we create new ones and send them back to the server.