Okay, but when’s the last time someone created a security vulnerability by sneakily taking over a Windows dependency controlled by a single developer after pressuring them into handing the keys over with a bunch of sockpuppets?
Okay, but when’s the last time someone created a security vulnerability by sneakily taking over a Windows dependency controlled by a single developer after pressuring them into handing the keys over with a bunch of sockpuppets?
IrritableOcelot@beehaw.org 1 month ago
Sure the threat model is different, I’m just saying it’s still a single point of failure.
millie@beehaw.org 1 month ago
It’s not, though. It’s a much wider potential for failure, as there are a great number of dependencies that are often left to individual developers to maintain. That may be a somewhat reasonable amount of risk when you’ve got multiple options for dependencies and no major target, but when the entire EU relies on single individual maintainers? That’s a massively exploitable threat vector. It would be absurd to assume no one will take advantage given what we’ve already seen.
It would be an extremely foolish move to put the whole EU’s security on one single set of open source dependencies. Microsoft at least has a financial and legal incentive to try to prevent straight up breaches by state actors, shitty as they may be. There’s no such resource allocation or responsibility when it comes to open source repos.