Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Silo’d, academic codebases are not under the kind of attacks that commodity software is


The silo'd codebases I was referring to are verification tools they produce. They're used to prevent attacks. Each tool has one or more capabilities others lack. If combined, they'd catch many problems.

Examples: KLEE test generator; combinatorial or path-bases testing; CPAChecker; race detectors for concurrency; SIF information flow control; symbolic execution; Why3 verifier which commercial tools already build on.


"Each lacks capabilities" is not a strong sell for "together they can catch most problems".




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: