rustup

> Why didn't the author sign it? Discussed here: https://github.com/rust-lang/rustup.rs/issues/1568 It boils down to that the authors have not gotten around to it and are not experts on Authenticode. Apparently the macOS binary is also not signed, so at least Windows isn't being singled out. To validate your binary you can use the SHA256 checksum that someone posted in the issue two days ago.

Incidentally the copy/rename process can run into issues on Windows due to Windows Defender holding a lock on the file which can prevent it being renamed. This is an issue for the Rust updater utility: https://github.com/rust-lang/rustup.rs/issues/1436

Note that there is an open issue to perform the self-update before the update: [0]. Could be a good first patch for someone looking to contribute :) [0] https://github.com/rust-lang/rustup.rs/issues/1838

The reqwest backend (which uses native-tls and thus schannel and thus the Windows cert store) is the default on Windows, so it shouldn't be using curl. https://github.com/rust-lang/rustup.rs/commit/6389676b6bf211... If you must use an older rustup, set `$env:RUSTUP_USE_REQWEST` (or `$env:RUSTUP_USE_HYPER` for an even older rustup) to `1`

The MITM proxy issue makes Rust a non-starter in many corporate environments. Unfortunately, when someone tried to make a first step, he was treated very poorly and his work was sabotaged. I don't have much hope that it will be addressed again soon: https://github.com/rust-lang/rustup.rs/pull/1624#pullrequest... It's really sad, because Rust started with the same good idea as Golang: treat Windows users as first-class citizens.

I've been waiting so much for a way to use rustup (and Cargo, but that's beyond the pull request a bit further down) behind a MITM proxy. And since Rust has always been Windows-friendly, I had high hopes when someone actually started to implement this support (basically pass "-k" to curl). Because I had fought with all kinds of git and curl configuration files, until I realized that those don't mean anything to rustup. The implementation was critiqued in a very civil way. The author fixed the issues. Everything was ready to merge and... in walk some busybodies who under the pretense of caring about security (having no clue about the issue or modern Windows workplaces, and despite clear refutations of their concerns) have seemingly been able to kill this patch: https://github.com/rust-lang/rustup.rs/pull/1624/ "We need to discuss this with