You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a first step before having tiered message encryption, we should encrypt every message with the team key. In storage.service:sendMessage, encrypt the message before adding it to the channel db.
Acceptance Criteria
Encryption mechanism / libraries pass review by e.g. Alishah or some other expert
Message model includes key name and generation
Messages get encrypted before being added to channel db
(maybe) Differentiate public and private channels, keep the publicChannelsRepo infrastructure as a way to send unencrypted messages, and add a privateChannelsRepo which gets encryption
(maybe) Pull channels functions out of StorageService, create a Channels module, and move all the message sending, receiving, encrypting, and decrypting logic there
The text was updated successfully, but these errors were encountered:
Description
As a first step before having tiered message encryption, we should encrypt every message with the team key. In storage.service:sendMessage, encrypt the message before adding it to the channel db.
Acceptance Criteria
The text was updated successfully, but these errors were encountered: