3 ms·
It's not really about "proving" something secure, but about leveling the playing field. With a piece of proprietary code, there is inherently a large differenc
by mindslight 11y ago
It's not really about "proving" something secure, but about leveling the playing field.
With a piece of proprietary code, there is inherently a large difference between the public and private analysis of that software. And that private information can be leveraged by traditional power structures of money/government, eg source sharing programs with surveillance agencies.
With Free software [0], one can be reasonably confident that the public analysis and private analysis are much closer. Nefarious groups can still spend resources to increase their private advantage, but the public baseline starts off much higher. And if the bad actors do start to exploit something, the public already has much more information with which to go about figuring it out.
As another poster said, it's necessary but certainly not sufficient.
[0] "open source" ersatz seems sufficient for such analysis, but generally implies a lack of ability to recompile. So who the hell knows what the binary is actually made from.
- krapp 11y ago>but the public baseline starts off much higher. Does it really? How many people are actually watching any particular piece of free/open source software, versus the number of programmers who might be paid to do so for the same as a proprietary project? The "public baseline" for free software includes all users, but only the subset of those who are competent enough programmers to be able to recognize issues, and who actually audit code and bring those issues to light, or have a PR accepted, or have the time to fork a project, even matter in this case. I suspect politics and popularity affect the security of open source projects far more than the openness of the source code itself. While the potential is there once an issue is discovered for the community to come together around a solution in ways a dedicated staff might not be able to achieve, unpopular but mission critical projects may languish for years with only one or two people watching them because everyone is watching code that looks good on their resume.
- mindslight 11y agoAny software can languish. Putting much trust in any under analyzed software is a poor idea. The money from a closed project can buy professional auditors, but their utility is permanently capped by users not knowing if the company retains privileged backdoors. A user can only trust the software as much as they can trust that company. And as interest in the software rises, interest in subverting the company does as well. Like always, centralization makes the small scale much easier but is fundamentally flawed when scaled up.