summaryrefslogtreecommitdiff
path: root/doc/HACKING/Fuzzing.md
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2020-07-13 10:45:04 -0400
committerNick Mathewson <nickm@torproject.org>2020-07-13 10:45:04 -0400
commitecb43ce21caccbdfe99b0e12cdce7f83d59b06e3 (patch)
tree972dfab41d90ef357b5f0881bb8a646f7896f23a /doc/HACKING/Fuzzing.md
parent0c91c63593720f07a20034bce2b0478dee216763 (diff)
parenteb427f309cbe2eb82769fdec4e9b7a7249c3287b (diff)
downloadtor-ecb43ce21caccbdfe99b0e12cdce7f83d59b06e3.tar.gz
tor-ecb43ce21caccbdfe99b0e12cdce7f83d59b06e3.zip
Merge branch 'maint-0.4.4'
Diffstat (limited to 'doc/HACKING/Fuzzing.md')
-rw-r--r--doc/HACKING/Fuzzing.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/HACKING/Fuzzing.md b/doc/HACKING/Fuzzing.md
index d140844bef..d9e133008a 100644
--- a/doc/HACKING/Fuzzing.md
+++ b/doc/HACKING/Fuzzing.md
@@ -28,7 +28,7 @@ have a reasonably recent clang and libfuzzer installed. At that point, you
just build with --enable-expensive-hardening and --enable-libfuzzer. That
will produce a set of binaries in src/test/fuzz/lf-fuzz-* . These programs
take as input a series of directories full of fuzzing examples. For more
-information on libfuzzer, see http://llvm.org/docs/LibFuzzer.html
+information on libfuzzer, see https://llvm.org/docs/LibFuzzer.html
Third, there's Google's OSS-Fuzz infrastructure, which expects to get all of
its. For more on this, see https://github.com/google/oss-fuzz and the
@@ -77,7 +77,7 @@ and then not actually use it.
Read afl/docs/notes_for_asan.txt for more details.
- Download recidivm from http://jwilk.net/software/recidivm
+ Download recidivm from https://jwilk.net/software/recidivm
Download the signature
Check the signature
```console