matrix-org / matrix-org/matrix-spec
voip call events leak internal IP addresses
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 330
- Forks
- 150
- Avg merge
- 2h 21m
- Merged PRs (30d)
- 3
Description
VoIP calling within Matrix (`m.call.invite`, `m.call.candidates`, `m.call.answer`) persists private call routing candidate IP addresses to the room history with every call, and they're there for ever.
We need to communicate the IP addresses to route the call, but that information would ideally not be stored in room history, or at very least would not be stored permanently.
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 reviewing the Matrix specification entries for m.call.invite, m.call.candidates, and m.call.answer, focusing on how candidate IP addresses are persisted in room history. Determine a protocol-level approach that still communicates routing information while preventing permanent exposure, and define completion as the specification documenting that behavior clearly.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking, security
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100