- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
You must log in or register to comment.
Thoughts and prayers.
I’m beginning to think this “NPM” thing isn’t a great idea.
Its always npm
I don’t really see how it’s NPM at fault here. This was caused by a malicious actor taking control of an account and putting out bad packages on it. It could happen on any package repository for any language
Trust by default for a atomic packaging system. Entirely NPM’s fault.
My understanding is that for most package managers the signing keys are held by a smallish number of maintainers responsible for entire sections, who presumably keep those accounts pretty tightly secured. Not impossible to take over, but it’s a smaller attack surface.
While for NPM as far as I know every uploader keeps their own account and there’s not even signing keys to lose control of.
I’m not familiar with npm but why is this always NPM? Is it a specific issue they have?
It’s a “package manager” that has zero integrity checks built in. Web devs also love it. Nice combination.
Culture problem imo.
What was the red hat meaning?
One day, back in 1995, I could download every red hat package onto a series of 13 floppies.
In fact, it was required if you wanted to install red hat. So was compiling them all onto your own computer.
How far we’ve come
Just use Linux!!
😁
Tough crowd, Jeez!
NPM is not a Linux thing - it’s to do with web applications, so it works on Windoze and Mac too.
Windoze? What’s that? Sounds like socialism 🤨 And I never eat hamburgers, just so you know
Should we tell them?
Sssssh! They are not ready yet for The Truth 😭
