News for hackers. Stuff that matters.
Re:Malicious code in the purescript NPM installer by pvg on Sunday July 28, 2019 @05:08PM (#20549845)
they piggybacked onto the existing DNS domain name control

It's a recommended and widely-followed voluntary naming scheme - it's not in any way connected to domain name control.

Re:Malicious code in the purescript NPM installer by vbezhenar on Sunday July 28, 2019 @05:13PM (#20549868)
But it's easy to connect to domain name control. Allow uploading to maven central only after domain verification. Java did not do that, AFAIK, but other languages can do that.
Re:Malicious code in the purescript NPM installer by neilv on Sunday July 28, 2019 @05:15PM (#20549877)
I should've been more clear about what I was saying with "control". The recommendation is connected directly to domain names you control. What was not done at the time was enforcing that, or using that as a basis of authentication or distribution, which is part of why I said more could be done, today.
Re:Malicious code in the purescript NPM installer by pvg on Sunday July 28, 2019 @05:47PM (#20549999)
The purpose of the scheme was to make namespace collisions less likely and that's about it, though. And people regularly deviate from it, both then and now. Not using it as a basis for authentication or distribution probably remains a really excellent idea.