matrix-org / matrix-org/matrix-spec
spec should be clearer about how to handle m.room.encryption events
Open
Nobody has claimed this yet.
A-Client-Server
A-E2EE
clarification
enhancement
security
- Dominant language
- HTML
- Stars
- 330
- Forks
- 150
- Avg merge
- 2h 21m
- Merged PRs (30d)
- 3
Description
For example, how to interpret:
m.room.encryptionevents that have been redacted- when you're in the room when the event is redacted
- when you join the room after the event is redacted and so don't see the original event
m.room.encryptionevents that are "invalid"- missing fields
- use an algorithm that you don't understand
- multiple
m.room.encryptionevents
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
Start by reading the Matrix specification sections covering m.room.encryption events and event redaction. Compare the behavior for redacted, invalid, and repeated encryption events, including the cases listed in the issue. Done means the specification explicitly defines how each case should be interpreted.
Written by the indexing model from the issue text.
Assessment
- Domain
- cryptography, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100