this post was submitted on 05 Mar 2024
130 points (87.4% liked)
Open Source
31359 readers
95 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This doesn't pass the smell test.
curlinshshisbash[^1][^1]:
sh <(curl -sSf https://url.redacted/script)Installing by piping from curl is pretty common and not a red flag in and of itself. Even Rust is installed this way. If you don't trust the URL, you also shouldn't trust any binary installers downloaded from that website.
Toxic. Speaking as someone who was security chief at an OS, what you meant to say was 'toxic'.
Given its insidious nature, though, 'venomous' may be a good alternate.
Rust is a red flag
Rust is an amazing programming language. No u
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.
Can you elaborate?
I was under the impression that there was some kind of consensus around rust being one of the safest languages to use. However, I've seen comments about rust being bad pop up in a few threads lately but they never explain why they think so.
You're talking about using the language and preventing errors. That's less about security and more about preventing errors.
I'm talking about the supply chain, watering hole attacks, etc. Crates does not cryptographically verify the authenticity or anything that it downloads.
The only language that I'm aware of that has a dependency manager that has cryptographic auth of everything it downloads is Java's Maven. Everything else is vulnerable, rust included.