2 ms·
I didn't get that sense from the article - he's not refusing to release the info for his own benefit, or to be a dick; he's ostensibly doing it because he feels
by potatolicious 17y ago
I didn't get that sense from the article - he's not refusing to release the info for his own benefit, or to be a dick; he's ostensibly doing it because he feels like this just encourages the "we'll fix stuff when other people find it in the wild" mentality, which doesn't help make software more secure in the long run.
He wants software producers to actively try to break their software so that his ostensibly simplistic tools can't find wide open holes like this.
I'm sure some egotism rolls into it somewhere, but I don't think it's altogether a bad stance... you shouldn't be waiting for your users to tell you where your security holes are.
- pxlpshr 17y agoyou shouldn't be waiting for your users to tell you where your security holes are. while I agree with that ideology, in reality you just can't assume that to be the case when you have multiple people touching the code, and features added regularly that may inadvertently introduce holes. what software has ever been 100% bullet proof? Also, I think that statement largely contradicts the notion of 'release early, iterate often' considering it's grounded on the notion of integrating feedback and bugs reported by users. Are major corporations held at a different standard simply because they have more resources? Even with thousands of employees, it's still a glass box compared to the millions that will use it.