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

Decrypt messages with team key #2632

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

Decrypt messages with team key #2632

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

We already store messages in the redux store after receiving them from OrbitDB, so until we prioritize work to move from the redux store to a better local storage solution we should just decrypt during the replicate and replicate.progress events in storage.service:subscribeToChannel and pass the decrypted message to the redux store. We can maintain a queue of messages that failed to decrypt in LevelDB until we have a better solution.

Acceptance Criteria

  1. Messages are decrypted in backend when replicated from OrbitDB and passed to Redux
  2. Messages which fail to decrypt are added to a queue and checked when the lockboxes a user can access change
@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