summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authordjm@openbsd.org <djm@openbsd.org>2016-09-16 06:09:31 +0000
committerDamien Miller <djm@mindrot.org>2016-09-21 11:07:47 +1000
commit920585b826af1c639e4ed78b2eba01fd2337b127 (patch)
tree4ad04c8b7550603630345d6731d2ce29ed0c7b38
parent0445ff184080b196e12321998b4ce80b0f33f8d1 (diff)
upstream commit
add a note on kexfuzz' limitations Upstream-Regress-ID: 03804d4a0dbc5163e1a285a4c8cc0a76a4e864ec
-rw-r--r--regress/misc/kexfuzz/README4
1 files changed, 4 insertions, 0 deletions
diff --git a/regress/misc/kexfuzz/README b/regress/misc/kexfuzz/README
index 8b215b5b..abd7b50e 100644
--- a/regress/misc/kexfuzz/README
+++ b/regress/misc/kexfuzz/README
@@ -26,3 +26,7 @@ A comprehensive KEX fuzz run would fuzz every packet in both
directions for each key exchange type and every hostkey type.
This will take some time.
+Limitations: kexfuzz can't change the ordering of packets at
+present. It is limited to replacing individual packets with
+fuzzed variants with the same type. It really should allow
+insertion, deletion on replacement of packets too.