libxml2: make binary name consistent

mykter · Feb 16, 2021 · d20b19d · d20b19d
1 parent e4b9d6d
commit d20b19d
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/challenges/libxml2/ANSWERS.md b/challenges/libxml2/ANSWERS.md
@@ -3,7 +3,7 @@ would provide the fuzzer with a comprehensive set of tokens that have special me
 
 Happily AFL ships with a ready made XML dictionary, so we can use that:
 
-    afl-fuzz -i in -o out -x ~/AFLplusplus/dictionaries/xml.dict ./harness @@
+    afl-fuzz -i in -o out -x ~/AFLplusplus/dictionaries/xml.dict ./fuzzer @@
 
 You should see the numbers of paths found grow much faster using this approach. Crucially, we'll also uncover a bug that
 would never be found without it.

diff --git a/challenges/libxml2/HINTS.md b/challenges/libxml2/HINTS.md
@@ -22,8 +22,8 @@ specified filename.
 Both of these approaches are good, but from here on we'll just look at the `xmlReadFile` option for simplicity.
 
 Once you've implemented the harness, compile it (refer back to README.md for the include & linker flags you need with
-libxml2), and then test your `harness` executable by specifying an XML file on the commandline, e.g.
-`./harness ./libxml2/regressions.xml`. There shouldn't be any visible result (unless you added some kind of output to
+libxml2), and then test your `fuzzer` executable by specifying an XML file on the commandline, e.g.
+`./fuzzer ./libxml2/regressions.xml`. There shouldn't be any visible result (unless you added some kind of output to
 your harness). We're now ready to fuzz in the usual manner for an ASAN-instrumented binary; here's a reminder of how to
 do it for the file-argument approach: