41–43 of 43 posts
Earlier quoted context omitted.
Friendly reminder that SELinux was developed by the NSA, and is now part of Linux. So clearly the open source community doesn't care too much about who created a piece of code. Case study 2: bitcoin.
Case study 1: the US Department of Defense created ARPANET, the first network to implement TCP/IP.
Earlier quoted context omitted.
Friendly reminder that SELinux was developed by the NSA, and is now part of Linux. So clearly the open source community doesn't care too much about who created a piece of code. Case study 2: bitcoin.
Case study 1: the US Department of Defense created ARPANET, the first network to implement TCP/IP.
Earlier quoted context omitted.
People tend to cite heartbleed as an example of how "open source" has no intrinsic security value. While I agree that something being "open source" does not automatically make it secure, I think that it does allow us to gauge the security of the project. In the case of heartbleed, anyone who has ever spent more than 30 seconds looking at OpenSSL can tell you that it is not secure software and never will be. We can't…
People that claim open source has no security value seem to believe that just because you can't catch every vulnerability through public review, you may as well not bother at all. That logic is obviously faulty, I can't imagine they would apply the same rationale to cancer screening.
Nice strawman you got there.