3 ms·
> My problem is that this weaponisation is killing off trust. Trust that all programmers started to place in open source maintainers maybe a decade ago out of
by scotty79 5y ago
> My problem is that this weaponisation is killing off trust.
Trust that all programmers started to place in open source maintainers maybe a decade ago out of sheer lazyness is absolutely insane.
Pulling freshest code out of thousand libraries automatically into the medium security project that you are building is absolutely crazy.
It's inviting thousand strangers to run code on your machine which contains your comercial creation and data. Without any protection whatsoever besides "trust" which is just another word for laziness and being hopeful.
The faster we can ditch this trust, the faster we will develop actual protections, vetting processes, delaying updates, caching, forking, so we can isolate our work from the thousands of wonderfull people all of which are one bad day from wiping all your files.
- musingsole 5y ago> Pulling freshest code out of thousand libraries automatically into the medium security project that you are building is absolutely crazy. But we have a test suite and a whole CI/CD pipeline to verify everything works! /s /Until you realize your tests only cover what they cover in the way they cover it. //Until you realize there is no test suite at all and it's all verified in production. ///It's not like you read the library's code until something was *really* broken or *super* slow anyhow.
- ahelwer 5y agoActually things are working quite well! These events remain remarkable news items. There are tremendous benefits to having an ecosystem built on trust and mutual assumption of good will. Transforming this into a scar tissue bureaucracy after some minor cuts is only one of several options. Another is to make choices like this so socially radioactive that only people with nothing to lose would ever make them. Trust is very valuable.
- scotty79 5y agoSystems are not working well. They are just working carelessly till the catastrophy. leftpad.js wasn't even malicious action. Just one developer withdrawing his code from the community. Imagine what would happen if one dev of popular package just had a nervous breakdown and did rm -fr / on his next update. Or delete the contents of the repo it is a dependancy of and do a force push. We have zero systems in place that could catch it before work of thousands of people is destroyed.
- genocidicbunny 5y agoOr worse, deploys something far more insidious. A keylogger that quietly sucks up your credentials for example.
- fartcannon 5y agoYeah. Competing interests. We can all slow down and work like real engineers do, with the same level of responsibility they take on, and check every line of code. OR we can just do whatever the fuck we want, solving our problems and/or making money. But if we do it without the rigor of real engineering, we can't exactly blame OSS or the devs that provide the OSS for this choice. It's entirely our fault if it goes south.
- deleted 5y ago[deleted]
- deleted 5y ago[deleted]
- hulitu 5y agoYou don't develop protections. You develop zero trust. Unfortunately the current OSs cannot distinguish zero trust programs.