matrix-org / matrix-org/matrix-spec
Should we kill device IDs, replacing them with hashes of your e2e device identity key?
Open
Nobody has claimed this yet.
A-Client-Server
A-E2EE
enhancement
- Dominant language
- HTML
- Stars
- 330
- Forks
- 150
- Avg merge
- 2h 21m
- Merged PRs (30d)
- 3
Description
Rather than having yet another ID to worry about and keep in sync with E2E etc, perhaps we should just make your device ID the same as your E2E public identity key now that we have E2E by default. (thanks to @Gargron & @jcgruenhage for the idea)
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
No files, tests, or entry points are named. Start by locating the Matrix specification sections that define device IDs and E2E public identity keys, then determine compatibility and synchronization implications; done requires a decided protocol direction and documented requirements.
Written by the indexing model from the issue text.
Assessment
- Domain
- cryptography, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100