| > If open sourcing your code presents any risk to sensitive personal information, then that means that you are already grossly mishandling this information This is also clearly false. For example, take this scenario: - You use web framework Omega, but minimise indicators of this (suppress HTTP headers, etc). - At 2am, a critical security vulnerability is discovered for Omega and a patch is released shortly after. - Malicious actors scrape GitHub to find sites that use Omega, and try compromise them. - At 9am, you apply this patch. If your project is open source, there is a 7 hour window where you are clearly and publicly broadcasting that you are vulnerable. If your project is not, there is a 7 hour window where you are vulnerable, but this is not easily apparent to attackers. How would you prevent this risk? |
Well - unless there is a targeted attack _against you_. In this case the attacker will search for known vulnerabilities in Omega and maybe even try to come up with some new ones. Having source helps the attackers here, but then again, it has helped researchers fix the vulnerabilities too. So it's a mixed blessing.