RocketChat / RocketChat/Rocket.Chat
No permission system for E2E
Open
Nobody has claimed this yet.
security
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
A relatively obvious one: I want to allow my users to use E2E for their own direct message channels. However, there seems to be no way to enable E2E (or even forced E2E) without making my users able to edit any room. What is the correct way to do this, or is there none?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating the existing E2E and room-permission implementation, then determine whether direct-message E2E can be enabled without granting room-edit permissions. Done means the supported permission behavior and its limits are defined and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Domain
- authorization, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100