Re:Alert: NPM modules hijacked
by henrikfr on Wednesday March 23, 2016 @11:35AM
(#11345389)
Insane, yes, but I guess it's just never really been that much of a problem until now. Hopefully something good will come out of this..
[ Parent
| on HN ]
> it's just never really been that much of a problem until now
That's a reasonable excuse in the 90s, before automatic updates over HTTP were common. Our industry now has decades of experience securing HTTP updates and package managers, with various Linux solutions demonstrating good practices.
Something similar is (or at least was) true for Github: I changed my username a couple of years ago and I recently found out that another user is now using my original username. Less of an issue due to the much longer timeframe, but I think not allowing username re-use would be a safer choice.
Re:Alert: NPM modules hijacked
by CorpOverreach on Wednesday March 23, 2016 @12:05PM
(#11345672)
You would think this is part of security 101 for these things...
And people wonder why big enterprises are scared of touching open source stuff.
> And people wonder why big enterprises are scared of touching open source stuff.
some open source stuff. Most enterprises dig distributions, especially with LTS.
Many big enterprises run on free software. Just because this particular free software project is a shit-show doesn't make all free software projects this bad.
Re:Alert: NPM modules hijacked
by FranOntanaya on Wednesday March 23, 2016 @12:49PM
(#11346087)
Module repositories have been a thing for decades. Even a platform as crusty-old as WordPress doesn't allow repository take-overs for plugins. Surely someone had some experience outside npm to think about this.