Active Entries
- 1: History Repeating Itself (Labour and ID cards edition)
- 2: The Sickening Has Me
- 3: Interesting Links for 06-06-2025
- 4: Interesting Links for 05-06-2025
- 5: Interesting Links for 04-06-2025
- 6: Why does Edinburgh Council hate cars?
- 7: Interesting Links for 02-06-2025
- 8: Interesting Links for 03-06-2025
- 9: Some thoughts on the UK and immigration
- 10: Interesting Links for 30-05-2025
Style Credit
- Style: Neutral Good for Practicality by
Expand Cut Tags
No cut tags
no subject
Date: 2018-03-16 01:06 pm (UTC)Another particularly annoying example of this is if you try to apply a fuzzer to some code that's not well set up to be fuzzable.
If you're using, say, AFL as your fuzzer, it likes command-line programs that it can feed stuff to on standard input and gradually tune for inputs that have interesting effects. So if you want to fuzz, say, a pile of library code that accepts input in the form of in-memory data structures, probably the first thing you do is write an AFL adapter, in the form of some sort of wrapper program that takes stuff on standard input, parses it into instances of those data structures, and calls the library routines on those in turn.
If you do this, you will inevitably spend the first week combing out the bugs AFL found in the new parsing code, and it's even money whether your patience will last long enough for AFL to start taking an interest in the code you actually wanted to test.
Two months of daily GTA causes no significant changes in behavior
What, not even being better at GTA? :-)