Restrict some blocked terms to word boundaries
This restricts /red.?line/ and /wtf/ to only match after a
word boundary, to avoid unintended matches such as
"configured line" and base64-encoded data that happens to have
the sequence "wtf" in it.
BUG=None
TEST=Ran search_blocked_words.sh with the new lists
Change-Id: I123b022838992058c6331f2f796e685dc08dc7eb
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/repohooks/+/2454295
Tested-by: Bob Haarman <inglorion@chromium.org>
Reviewed-by: Bernie Thompson <bhthompson@chromium.org>
Reviewed-by: Chris McDonald <cjmcdonald@chromium.org>
Commit-Queue: Bob Haarman <inglorion@chromium.org>
diff --git a/blocked_terms.txt b/blocked_terms.txt
index aafb300..9d54a7d 100644
--- a/blocked_terms.txt
+++ b/blocked_terms.txt
@@ -24,7 +24,7 @@
master
mitm
\bnative
-red.?line
+\bred.?line
rtfm
sane
sanity
@@ -33,4 +33,4 @@
white.?hat
white.?label
white.?list
-wtf
+\bwtf
diff --git a/unblocked_terms.txt b/unblocked_terms.txt
index b7768d7..6fc5f2b 100644
--- a/unblocked_terms.txt
+++ b/unblocked_terms.txt
@@ -35,7 +35,7 @@
master
mitm
\bnative
-red.?line
+\bred.?line
rtfm
sane
sanity
@@ -44,4 +44,4 @@
# white.?hat
white.?label
white.?list
-wtf
+\bwtf
