summaryrefslogtreecommitdiff
path: root/astraceroute.8
diff options
context:
space:
mode:
authorTobias Klauser <tklauser@distanz.ch>2020-06-19 14:46:31 +0200
committerTobias Klauser <tklauser@distanz.ch>2020-06-19 14:46:31 +0200
commitd8cb8692174a3f963185c93420662d8207668f78 (patch)
tree091e44e8d843f7b0caac8e7323d1bfaa9008d3f7 /astraceroute.8
parentc6dd9abd8d7a5332d0c1078196528926054791ae (diff)
astraceroute.8: use more sensitive terminology
Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
Diffstat (limited to 'astraceroute.8')
-rw-r--r--astraceroute.88
1 files changed, 4 insertions, 4 deletions
diff --git a/astraceroute.8 b/astraceroute.8
index fc999aa..80d24f0 100644
--- a/astraceroute.8
+++ b/astraceroute.8
@@ -24,9 +24,9 @@ ISP name. astraceroute also displays timing information and reverse DNS data.
Due to astraceroute's configurability, it is also possible to gather some more
useful information about the hop regarding what it does and does not allow to pass
through. This is done by using clear text strings for probing DPIs or
-``great firewalls'' to determine if they will filter out blacklisted critical
-keywords. This tool might be a good start for further in-depth analysis of such
-systems.
+``great firewalls'' to determine if they will filter out blocked critical
+keywords. This tool might be a good start for further in-depth analysis
+of such systems.
.PP
.SH OPTIONS
.TP
@@ -159,7 +159,7 @@ and do a TCP Xmas probe this time.
In this example, we have a Null probe to the remote host netsniff-ng.org, port
80 (default) and this time, we append the cleartext string "censor-me" into the
packet payload to test if a firewall or DPI will let this string pass. Such a trace
-could be done once without, and once with, a blacklisted string to gather possible
+could be done once without and once with a blocked string to gather possible
information about censorship.
.PP
.SH NOTE