summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJoseph Bisch <joseph.bisch@gmail.com>2017-05-12 18:45:23 -0400
committerJoseph Bisch <joseph.bisch@gmail.com>2017-05-12 18:45:23 -0400
commit7dc04453b05c3eaf2aa3b02d951f1538716aa16c (patch)
tree839a09323d9afc497b61d382ec34b4593dec47e0
parentdcf419f2f055c91e8ae84da1530fab35cee97080 (diff)
downloadirssi.github.io-7dc04453b05c3eaf2aa3b02d951f1538716aa16c.zip
fix images in fuzzing post
-rw-r--r--_posts/2017-05-12-fuzzing-irssi.markdown4
1 files changed, 2 insertions, 2 deletions
diff --git a/_posts/2017-05-12-fuzzing-irssi.markdown b/_posts/2017-05-12-fuzzing-irssi.markdown
index 8378111..4afeb1e 100644
--- a/_posts/2017-05-12-fuzzing-irssi.markdown
+++ b/_posts/2017-05-12-fuzzing-irssi.markdown
@@ -117,7 +117,7 @@ data from stdin.
Here is an image showing the AFL UI that displays:
-![AFL UI](images/afl_nocrash.png)
+<img src="/images/afl_nocrash.png" />
As you can see no crashes have been found so far during that fuzzing session.
AFL has found a total of 3090 inputs that cause new paths to be taken and
@@ -131,7 +131,7 @@ indication that something is wrong, but in this case the program is just a
simple program that AFL can't find any additional paths through, hence the
warning.
-![AFL UI with crash](images/afl_crash.png)
+<img src="/images/afl_crash.png" />
Now we can go to `afl/out/crashes` in our program's source tree and find crashes
with filenames like `out/crashes/id:000000,sig:06,src:000000,op:havoc,rep:32`,