piping random scripts from the internet into bash is the worst way of installing things. imagine if there was an operating system where this was the main way of installing things, and people just googled the program name, clicked the first link, and ran an executable file with admin permissions. imagine that
Ironically has security equivalent to most Linux package repositories.
Removing other folks from the thread. I don't really want to get into a rock-em-sock-em debate since I said my original comment only half seriously.
But seriously for a moment, what you said is a value judgement. You're telling me what you have decided to do, but I think an awful lot of people implicitly trust ISVs. Unless you're using a heavily sandboxed OS like Qubues or iOS, it seems like a pretty intense trust relationship. Both are equally applicable, although they can have different consequences.
By the logic you've laid out, you're making a case I should trust Microsoft and Ubuntu equally since I use both their platforms, but that's not true. So I can't help but remain unconvinced by it.
How many personal PPAs have you added? Are those different?
So I guess you just run old software all the time. Which is a luxury I wish I had. :)
Cool, but. We're so far afield of the original point. Anyone who can run void Linux can safely is a curl sh download, and their security standards are even more obscure.
The simple reality is that curl|sh gets much more hate than ppa's or build-from-source or "download this Deb" and folk's response is, "I super trust that those minimal requirements my OS put down are enough to make our pre-shared public key trust root safe."
But I see this as analogous to NodeJS's woes. All it will take is one person to get control of a critical package and slow roll and issue and we'll all be in the same boat.
That's why I use Qubes when I can. Then, I can actually use a computer like a human and have some degree of confidence that if I use it on a day when my judgement is impaired I'm not automatically totally fucked.
As a general rule, I object to creating security whipping targets because they tend to give a false sense of security to people. Hence I like pointing out curl https:// | sh is essentially a model that lots of people already are trusting.
The response is often "nuh-uh!" but you'll note the thread author here pretty much saw what I was saying and agreed as opposed to trying to lawyer their way into being right.
Maintainers are authority, and around these parts we demand authority justifies itself.
I don't know if void Linux has done that for you, but none of the OS's we have discussed here have sufficiently done it for me except the ones with hard segmentation.
Systemd is not cost me millions of dollars the way runit has, and it's less monolithic than runit. I humbly suggest that you give OSs using it a chance.
Not just because there's a lot of FUD about it, it also because fast boots are security feature. The enable you to turn off your computer more, Which intern makes you much more resistant to cold boot attacks.
Systemd is not a single binary.
The existence of a binary named systemd does not make systemd monolithic. Last I checked it had over 60 binaries, most of which are minimally privileged short lived daemons.
This is why I also mention systemd. Lots of lies floating around about it.
Do you know who did that vetting or what their criterion was? Or how often they vet?
That is a thing SSL certs can do.
Thinking on it, maybe the big advantages of packages is that they tend to have a signature over all the binary files as opposed to the status quo of bash scripts leading to other hard-to-audit downloads, and take that as an atomic unit.
It's not really harder to make a package do a dumb thing, but you have less reason to.
A bunch of technomancers in the fediverse. Keep it fairly clean please. This arcology is for all who wash up upon it's digital shore.