Validation of `Signer`'s `SignatureScheme` in `MlsGroup` APIs
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1k
- Forks
- 180
- Avg merge
- 3d 20h
- Merged PRs (30d)
- 18
Description
Currently, the signature scheme of the provided Signer is not validated by MlsGroup::update_group_context_extensions() and other APIs on MlsGroup that create commits.
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 with MlsGroup::update_group_context_extensions() and inspect the other MlsGroup APIs that create commits. Trace how the provided Signer is used and determine where its SignatureScheme should be checked; done means mismatched schemes are rejected consistently by all relevant commit-creating APIs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100