←back to thread

364 points Klasiaster | 6 comments | | HN request time: 0.478s | source | bottom
1. prmoustache ◴[] No.41857207[source]
> docker run -it --privileged --network=host --device=/dev/kvm -v $(pwd)/asterinas:/root/asterinas asterinas/asterinas:0.9.3

Is that the new generation of curl | bashism in action?

replies(3): >>41857251 #>>41858101 #>>41859535 #
2. wslh ◴[] No.41857251[source]
Is the "--privileged" option ironic here? The project is very interesting, but it feels a bit pedantic, especially when emphasizing Rust's safety features while downplaying Linux. At the same time, it seems they're not fully applying those principles themselves, which makes it feel like they're not quite 'eating their own lunch'.
replies(1): >>41857527 #
3. prmoustache ◴[] No.41857527[source]
A bit below in the github readme there is a link to the handbook where they explain how to build and run the project using cargo:

https://asterinas.github.io/book/osdk/guide/run-project.html

4. oefrha ◴[] No.41858101[source]
Hardly different from downloading random binary installers and executing them. Or random source distributions and (sudo) make install. Or npm/pip/cargo/etc. install random packages. Before anyone mentions distros and package managers, as a former team member of a major package manager I can assure you we don’t vet shit beyond project notability, and new versions are accepted semi-automatically. We’ll yank something after the fact if you report a malicious update, sure.

curl | bash has an actual problem: potential execution of an incomplete script (which can be mitigated with function calling). And there’s the mostly theoretical problem of the server being pwned / sending malicious code just to you (which of course also applies to any other unsigned channel). Arbitrary code execution is never a problem unique to it, but people dunk on it all the time because they saw another person dunking on it in the past.

replies(1): >>41859808 #
5. ◴[] No.41859535[source]
6. hnfong ◴[] No.41859808[source]
> as a former team member of a major package manager I can assure you we don’t vet shit beyond project notability, and new versions are accepted semi-automatically

An example that illustrates this: https://lwn.net/Articles/22991/

(And wow, it's been 22 years already...?)