Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Encrypt messages with team key #2631

Open
adrastaea opened this issue Oct 8, 2024 · 0 comments
Open

Encrypt messages with team key #2631

adrastaea opened this issue Oct 8, 2024 · 0 comments
Labels
e2ee end-to-end encryption lfa Features related to local-first-web/auth implementation

Comments

@adrastaea
Copy link
Collaborator

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

  1. Encryption mechanism / libraries pass review by e.g. Alishah or some other expert
  2. Message model includes key name and generation
  3. Messages get encrypted before being added to channel db
  4. (maybe) Differentiate public and private channels, keep the publicChannelsRepo infrastructure as a way to send unencrypted messages, and add a privateChannelsRepo which gets encryption
  5. (maybe) Pull channels functions out of StorageService, create a Channels module, and move all the message sending, receiving, encrypting, and decrypting logic there
@adrastaea adrastaea added e2ee end-to-end encryption lfa Features related to local-first-web/auth implementation labels Oct 8, 2024
@adrastaea adrastaea moved this to Backlog - Desktop & Backend in Quiet Oct 8, 2024
@adrastaea adrastaea added this to Quiet Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
e2ee end-to-end encryption lfa Features related to local-first-web/auth implementation
Projects
Status: Backlog - Desktop & Backend
Development

No branches or pull requests

1 participant