Support key updates independent of membership changes
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Domain
- cryptography
Research direction
The issue names no file, test, or entry point. Start by reviewing the mls-webapi-explainer content to determine where key refresh behavior belongs and define the expected change for refreshes without membership changes. Done requires agreed scope and acceptance criteria, which the payload does not provide.
Written by the indexing model from the issue text.
Description
MLS clients may need to refresh their key material even when no members are being added or removed.
- Dominant language
- No language data
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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.
Similar issues
-
security
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
IBM/OpenJCEPlus#1822 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
objects
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
snapshot-labs/snapshot.js#1247 · 1 comment ·