And? You are literally installing someone else’s code. The compiler isn’t an AV. This is true for all langs.
piping curl to bash for installing rust Dev tools
How is it any different than installing binaries from the site and just pulling the binary via curl?
The bash script is also visible to anyone, feel free to check it for anything that might be malicious.
Trust is a thing. We should trust the person writing our dependencies and be able to verify that it was published by them, and not somebody in the middle maliciously altering the code.
You should not be installing unsigned binaries from a website. Either use a package manager that checks for signatures or manually check the signatures yourself. If the project doesn’t sign their releases, open a bug report.
Why?
Crates is insecure and, as pointed out above, so is piping curl to bash for installing rust Dev tools
And? You are literally installing someone else’s code. The compiler isn’t an AV. This is true for all langs.
How is it any different than installing binaries from the site and just pulling the binary via curl? The bash script is also visible to anyone, feel free to check it for anything that might be malicious.
@Asudox @delirious_owl
There are many much safer ways of installing someone else’s code than curl|bash. It doesn’t even verify any signatures…
Trust is a thing. We should trust the person writing our dependencies and be able to verify that it was published by them, and not somebody in the middle maliciously altering the code.
You should not be installing unsigned binaries from a website. Either use a package manager that checks for signatures or manually check the signatures yourself. If the project doesn’t sign their releases, open a bug report.