Tracking: Trust model for signed Rust / Rustup releases
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 22h 40m
- Merged PRs (30d)
- 46
Description
Once we have simplistic signature checking in place (#2028) we need to decide upon and deploy a more comprehensive trust model so that we're not doing the bare minimum to protect our users.
- Meeting between relevant parties (e.g. Sequoia-PGP team, Infra team, Rustup team, and DKG) to kick off a working group
- That working group to discuss and come up with a functional trust model which improves on the status quo
- Implementation of that trust model in rustup.
People who might be relevant to this are:
- @kinnison - Rustup
- @pietroalbini - Infra/Release
- @nwalfield - Sequoia PGP
Obviously we will not limit the wg to those, but that's a starting point.
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 issue #2028 and the existing simplistic signature checking in rustup. The listed parties should form a working group to define a functional trust model, then implement it in rustup; done means the working-group discussion, trust model, and implementation are complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- release, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100