rust-lang / rust-lang/rustup

Sign the rustup install script

Open
#4,576 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Rust
Stars
7k
Forks
1.1k
Avg merge
22h 40m
Merged PRs (30d)
46

Description

Problem you are trying to solve

Over on arch the notes on Rust say something like "You've got two mutually exclusive choices for installing rust: pacman / rustup"

Arch goes on to say something like "... if you want to use Rust for development, use rustup etc."

Ok, so I want to use the rustup install script. But I also want to check what it's doing or alternatively check that it has been signed by the official rust team.

Do you guys publish signatures for the install script?
If so, is there a formal (scriptable) mechanism for verifying the install script via these signatures?

Cheers

Solution you'd like

Official Rust Team:

  1. crytographically signs each released version of the rustup installation script using an appropriate mechanism
  2. publishes public signing keys via multiple public channels
  3. publishes notifications of changes to signing keys using appropriate mechanisms
  4. publishes the signature for the current installer hosted on https://sh.rustup.rs
  5. specifies the formal process of obtaining and verifying public signing keys AND using the verified keys for the purpose of corroborating the rustup installation script via its digital signature
Notes

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the current installer hosted at https://sh.rustup.rs and the issue's requested signing, key-publication, rotation-notification, and verification process. Done means the Rust team has an agreed cryptographic mechanism, published verification keys and change notifications, and a formal scriptable procedure for verifying each released installer.

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
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.