Daniel Silverstone

@therealbstern No we don't sign rustup releases yet, only rust channels. We're working on some basic signature support by dint of unifying how rustup and rust releases are done to...

That's still opportunistic. If we want to *force* 1.3 we'd need to say `--tlsv1.3` surely?

Sounds like @sanmai-NL is right then, perhaps we just accept that we'll opportunistically upgrade to 1.3 on almost every platform and not worry too much about the few left that...

Unit tests belong in the crate, not in `tests/` which is where we have our integration tests. There is the `TestProcess` struct in the `currentprocess` module which is provided for...

Could we essentially do a "for each installed toolchain, uninstall toolchain, then uninstall self` in the uninstallation pathway? It'd be a tad more long-winded than our current approach, but it...

This is an interesting idea. Doing this would "reserve" the toolchain name "rust-version" but perhaps we can come up with some other term if that annoys anyone. To make this...

We do care we care greatly. Sadly while we have someone volunteering to help us with sorting out code-signing, it is a complex logistical problem because there's not (yet) a...

@rtrusso Next to each binary of `rustup-init` there is an associated SHA256 checksum available. This is the same URL, with `.sha256` added and is used by `rustup` to validate downloads...

> @kinnison can you please show us URL for the .sha256 checksum file of rustup-init.exe? Sure, the URLs are of the form: `https://static.rust-lang.org/rustup/archive/$VERSION/$TRIPLET/rustup-init$EXE$SUFFIX` Where `$VERSION` is something like `1.19.0` and...

We're still waiting for the foundation to reach a point that infra can deal with setting up key storage etc. @jethrogb 's offer is definitely in their notes for when...