From 920585b826af1c639e4ed78b2eba01fd2337b127 Mon Sep 17 00:00:00 2001 From: "djm@openbsd.org" Date: Fri, 16 Sep 2016 06:09:31 +0000 Subject: upstream commit add a note on kexfuzz' limitations Upstream-Regress-ID: 03804d4a0dbc5163e1a285a4c8cc0a76a4e864ec --- regress/misc/kexfuzz/README | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/regress/misc/kexfuzz/README b/regress/misc/kexfuzz/README index 8b215b5bf..abd7b50ee 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. -- cgit v1.2.3