element-hq / element-hq/element-meta
Configurable Key Forwarding strategy in SDK
- Dominant language
- No language data
- Stars
- 112
- Forks
- 25
- Avg merge
- 6h 6m
- Merged PRs (30d)
- 4
Description
## Objective
Clarify cross platform message key forward strategy, allowing to share more or less depending on needs and taking advantage of cross-signing.
## Prosposal
Define a KeyForwardingStrategy configuration in Matrix SDK:
Level 0 -> No Forwarding
Level 1 -> Forward Re-share if it was previously shared
Level 2 -> Level 1 + Forward to current user verified sessions
Level 3 -> Level 2 + Forward if the key was initially shared with another device belonging to the same verified user identity
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Start by reviewing the proposed four-level KeyForwardingStrategy alongside the SDK's existing cross-signing and key-sharing behavior, then define the configuration scope and acceptance criteria for each forwarding level.
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
- Mostly clear
- Newbie friendliness
- 25/100