3 ms·
It’s up to the person choosing and deploying the software to decide if the OSS project is sufficiently secured. This is the person (or party) who should shoulde
by pharmakom 3y ago
It’s up to the person choosing and deploying the software to decide if the OSS project is sufficiently secured. This is the person (or party) who should shoulder the blame. I don’t see why someone pushing to GitHub or whatever should have any responsibility for how their stuff is misused.
- LadyCailin 3y agoFollowed to its logical end, this also destroys open source as we know it today. If I’m going to have to vet your OSS with a fine tuned comb before I use it, I might as well just write it myself, and also be unencumbered from whatever license you chose. Only projects backed by FAANG would actually be used then.
- anthk 3y agoThen watch the ActiveX disaster and Blaster coming back but by 20000. Worst Botnet/ransomware attack from NK/Russia ever. The UE on HUGE losses. BSD and GNU depending companies almost get bankrupt overnight. Productivity halts with a worse outcome than COVID.
- rini17 3y agoIt does not work so well in practice. Projects like sqlite and curl had to take steps to hide themselves from end users, who are grasping at straws in face of malfunctioning product.