3 ms·
I wrote a rudimentary fuzzer at work for the sole purpose of generating core dumps. It worked so well that I got a stern talking to about not helping them relea
by 2OEH8eoCRo0 6y ago
I wrote a rudimentary fuzzer at work for the sole purpose of generating core dumps. It worked so well that I got a stern talking to about not helping them release the software.
- Forge36 6y agoDid they expect to release in a non working state?
- kelnos 6y agoMost companies, for better or worse, value time to market over fixing every last bug.
- andrei 6y agoBasic fuzzers can surprisingly go a long way. Barton Miller (the professor who first coined the term fuzzing), actually wrote a paper last year [0] where he just ran a very basic fuzzer against a bunch of common UNIX tools. Even after all these years of testing/usage, they still managed to find a ton of issues. [0]: https://arxiv.org/pdf/2008.06537.pdf https://arxiv.org/pdf/2008.06537.pdf
- Forge36 6y agoIsn't that the 1995 paper? The original study was 1990. He was my teacher, and he taught this in class :) I'm pretty sure his fuzzer was "for each file in system send as input to program X" That was the original tool, revisited was repeating the original test (might have tested against more programs which had become common since then)
- andrei 6y agoArgh, this is the paper I meant to link: https://arxiv.org/pdf/2008.06537.pdf https://arxiv.org/pdf/2008.06537.pdf (Updated the above comment as well)
- neolog 6y agoSounds like it didn't work very well for the task of finding significant bugs?