no comments (yet)

sorted by: hot top controversial new old
there doesn't seem to be anything here
19 comments in c/cybersecurity@sh.itjust.works view that post
[–] 48 points 5 months ago (9 children)

I'm beginning to think this "NPM" thing isn't a great idea.

  • source
  • hideshow 9 child comments
  • [–] 4 points 5 months ago (3 children)

    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

  • source
  • parent
  • hideshow 3 child comments
  • [–] 6 points 5 months ago (1 child)

    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.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 3 points 5 months ago (3 children)

    I'm not familiar with npm but why is this always NPM? Is it a specific issue they have?

  • source
  • parent
  • hideshow 3 child comments
  • [–] 10 points 5 months ago*

    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

  • source
  • [–] 2 points 5 months ago
    [–] 1 point 5 months ago

    What was the red hat meaning?

  • source
  • [+] -10 points 5 months ago* (5 children)