2 ms·
Two schools of thought, with the assumption that as you said no secrets, keys etc are in code. Open sourcing it allows the people to provide you with feedback
by davismwfl 11y ago
Two schools of thought, with the assumption that as you said no secrets, keys etc are in code.
Open sourcing it allows the people to provide you with feedback how to make it more secure or help find vulnerabilities so you can address them right away.
Not open sourcing it, prevents people from finding vulnerabilities which they could use to compromise your site, or other sites based on your code.
My own two cents, if you want to open source it, I'd do it and just value the feedback you will get and make things as tight as possible. A lot of times code doesn't get open sourced not because people are afraid of security but afraid of being judged by what they had to hack together to get 1.0 out, and then how long that code sometimes hangs around. Speaking from experience on this for sure.
- alexggordon 11y agoYeah, and that's the thing. If I do have bugs, I'd rather know about them and potentially let someone else learn from them, than simply solving security through it being closed source (the definition of "security through obscurity"). Thanks for the two cents!