Skip to content

Commit

Permalink
PR #173 - Fix incorrect info about bc
Browse files Browse the repository at this point in the history
  • Loading branch information
andreas-zeller committed Jan 18, 2024
1 parent 297d445 commit 4e56243
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion notebooks/Fuzzer.ipynb
Expand Up @@ -1201,7 +1201,7 @@
"source": [
"## Bugs Fuzzers Find\n",
"\n",
"When Miller and his students ran their first fuzzers in 1989, they found an alarming result: About **a third of the UNIX utilities** they fuzzed had issues – they crashed, hung, or otherwise failed when confronted with fuzzing input \\cite{Miller1990}. This also included the `bc` program, above. (Apparently, the bugs have now been fixed!)\n",
"When Miller and his students ran their first fuzzers in 1989, they found an alarming result: About **a third of the UNIX utilities** they fuzzed had issues – they crashed, hung, or otherwise failed when confronted with fuzzing input \\cite{Miller1990}. This also included the `bc` program, above. (The `bc` above is a [modern reimplementation](https://git.gavinhoward.com/gavin/bc) whose author is a [staunch believer in fuzzing](https://git.gavinhoward.com/gavin/bc/src/branch/master/tests/fuzzing)!)\n",
"\n",
"Considering that many of these UNIX utilities were used in scripts that would also process network input, this was an alarming result. Programmers quickly built and ran their own fuzzers, rushed to fix the reported errors, and learned not to trust external inputs anymore."
]
Expand Down

1 comment on commit 4e56243

@gavinhoward
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry for the comment, but this is missing "the predecessor of" which might make the parenthetical confusing.

Please sign in to comment.