summaryrefslogtreecommitdiff
path: root/trafgen.8
diff options
context:
space:
mode:
authorKartik Mistry <kartik.mistry@gmail.com>2014-05-02 11:10:57 +0530
committerTobias Klauser <tklauser@distanz.ch>2014-05-03 13:39:55 +0200
commit5381fe4fed17e813d41424ae29995d8624197a54 (patch)
tree5e6fc601789ddc558aa2f29d036219f7add17648 /trafgen.8
parent7aa9f970e88382f2508ee55122e27cdcfd8cdbda (diff)
doc: Fix typos in mausezahn and trafgen manpages
Fixed typos in mausezahn.8 and trafgen.8 [tklauser: Slightly edited commit message] Signed-off-by: Kartik Mistry <kartik.mistry@gmail.com> Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
Diffstat (limited to 'trafgen.8')
-rw-r--r--trafgen.82
1 files changed, 1 insertions, 1 deletions
diff --git a/trafgen.8 b/trafgen.8
index 6f4b806..4a888c5 100644
--- a/trafgen.8
+++ b/trafgen.8
@@ -427,7 +427,7 @@ For smoke/fuzz testing with trafgen, it is recommended to have a direct
link between the host you want to analyze (''victim'' machine) and the host
you run trafgen on (''attacker'' machine). If the ICMP reply from the victim
fails, we assume that probably its kernel crashed, thus we print the last
-sent packet togther with the seed and quit probing. It might be very unlikely
+sent packet together with the seed and quit probing. It might be very unlikely
to find such a ping-of-death on modern Linux systems. However, there might
be a good chance to find it on some proprietary (e.g. embedded) systems or
buggy driver firmwares that are in the wild. Also, fuzz testing can be done