3 ms·
I wrote a quick rundown of it on Schneier's blog discussing liability: https://www.schneier.com/blog/archives/2011/09/an_interesting.html#c595111 https://www.s
by nickpsecurity 10y ago
I wrote a quick rundown of it on Schneier's blog discussing liability:
https://www.schneier.com/blog/archives/2011/09/an_interesting.html#c595111 https://www.schneier.com/blog/archives/2011/09/an_interestin...
Idea being we just combine the right features, often standardized in libraries, with the most cost-effective of assurance activities proven to work. I gave a list of the latter to pick and choose from in another discussion:
https://news.ycombinator.com/item?id=10734477 https://news.ycombinator.com/item?id=10734477
Cleanroom methodology with safer languages with test-case generation, battle-tested libraries for common risk areas (esp web attacks or crypto), automation of parsing/protocol handling, static analysis to eliminate common issues, and basic code review would knock out vast majority of code-injections.