The suggestion of the website is certainly not great, but note that: * It has been improved a little by the https and tls 1.2 parameters compared to earlier ve

The suggestion of the website is certainly not great, but note that: * It has been improved a little by the https and tls 1.2 parameters compared to earlier versions that didn't have these params * You are not required to install rustup that way. There are many rustup packages available in distros today. Arch has one, nix OS has one. Debian is dragging their feet [0] but they aren't entirely opposed to the idea, so maybe something will change about this in the future. * Even if the download process is secured, rustup doesn't really verify any signatures, it just downloads what's inside the manifest. So you can download potentially malicious code if the S3 bucket is hacked that rustup downloads the compiler from. * Even if the entire process of obtaining rustc is secured, the standard way of using rust + cargo basically gives maintainers access to your local computer through build.rs and other methods. You can sandbox the cargo invocation, but who does that? [0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955208 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955208