Re:Backdoor in event-stream library dependency
by kevin_b_er on Monday November 26, 2018 @12:46PM
(#18535237)
Yes. The fast moving package management dependency hell seems to be spreading, but I believe its root comes from npm/javascript. If we see it elsewhere it is because it is borrowed from javascript as it was seen as "the future" of software development.
Re:Backdoor in event-stream library dependency
by pcwalton on Monday November 26, 2018 @02:32PM
(#18536118)
The concept of code sharing—which is a good thing, this incident notwithstanding—goes all the way back to CPAN and Perl 5.
Re:Backdoor in event-stream library dependency
by dragonwriter on Monday November 26, 2018 @07:02PM
(#18537977)
> The concept of code sharing—which is a good thing, this incident notwithstanding—goes all the way back to CPAN and Perl 5.
The concept is significantly older, but the implementation of a systematic facility for it rather than more ad hoc mechanisms may date from then. (It's a lot harder to sneak in and use an exploit in books of source code used in the 1970s-80s, though; convenience comes with a price.)
Re:Backdoor in event-stream library dependency
by tomjakubowski on Monday November 26, 2018 @03:35PM
(#18536567)
In case anyone is unfamiliar with Perl's version history like I was, Perl 5 and CPAN date to 1994.
Most programming languages have this issue to one degree or another, which is that they have a package management repository where there is no curation of content, and generally no package signing (there are some cases where that exists, but the take-up isn't always great).
The challenge is that this now seems to be embedded in the culture of a lot of development, and changing that culture would be very challenging, I'd imagine.