|
| 1 | +# EDIT THIS FILE AS YOU LIKE TO ADD OR REMOVE ANY BAD WORDS YOU WANT TO SCAN FOR ### |
| 2 | + |
| 3 | +### VERSION INFORMATION # |
| 4 | +################################################### |
| 5 | +### Version: V4.2019.07 |
| 6 | +### Updated: 2019-06-24 |
| 7 | +################################################### |
| 8 | +### VERSION INFORMATION ## |
| 9 | + |
| 10 | +############################################################################## |
| 11 | +# _ __ _ # |
| 12 | +# / |/ /__ _(_)__ __ __ # |
| 13 | +# / / _ `/ / _ \\ \ / # |
| 14 | +# /_/|_/\_, /_/_//_/_\_\ # |
| 15 | +# __/___/ __ ___ __ ___ __ __ # |
| 16 | +# / _ )___ ____/ / / _ )___ / /_ / _ )/ /__ ____/ /_____ ____ # |
| 17 | +# / _ / _ `/ _ / / _ / _ \/ __/ / _ / / _ \/ __/ '_/ -_) __/ # |
| 18 | +# /____/\_,_/\_,_/ /____/\___/\__/ /____/_/\___/\__/_/\_\\__/_/ # |
| 19 | +# # |
| 20 | +############################################################################## |
| 21 | + |
| 22 | +# This is merely an example and gets auto included as since Version 2.2017.07 introduced on 2017-04-20 |
| 23 | +# This file must exist on your system or Nginx will fail a reload due to a missing file |
| 24 | +# For all intensive purpose you can delete everything inside this file and leave it |
| 25 | +# completely blank if you do not want your Nginx Blocker to include scanning for bad words within urls or referrer string |
| 26 | +# Only add one entry per line |
| 27 | + |
| 28 | +# ******************************* |
| 29 | +# !!! WARNING WARNING WARNING !!! |
| 30 | +# ******************************* |
| 31 | + |
| 32 | +# *************************************** |
| 33 | +# PLEASE BE VERY CAREFUL HOW YOU USE THIS |
| 34 | +# *************************************** |
| 35 | +# Here is an example of how one supposed bad word can cause your whole site to go down. |
| 36 | +# An issue was logged where the users own domain name was specialisteparquet.com |
| 37 | +# Because this list contained the word "cialis" it was detected within his domain name causing |
| 38 | +# his entire site to go down and not server any assets. |
| 39 | +# That one entry would even cause any site containing a word like "specialist" anywhere in any |
| 40 | +# of their sites pages to cause them to be blocked and whitelisting your own domain name in the |
| 41 | +# whitelist-domains.conf file will not even bypass this, SO BE CAREFUL PLEASE |
| 42 | + |
| 43 | +# Think very carefully before you add any word here |
| 44 | + |
| 45 | +# ***************************************************************************************** |
| 46 | +# PLEASE MAKE SURE that you use word regex boundaries to avoid false positive detection !!! |
| 47 | +# ***************************************************************************************** |
| 48 | + |
| 49 | +# BY DEFAULT ALL THE EXAMPLES BELOW ARE COMMENTED OUT AND HENCE NOT ENABLED |
| 50 | + |
| 51 | +# As you can see in the examples below the word "adultgalls" is entered with a preceding \b and an ending \b |
| 52 | +# this makes it now "\badultgalls\b". It is crucial to use the word boundaries regex formatting. |
| 53 | + |
| 54 | +# --------- |
| 55 | +# EXAMPLES: |
| 56 | +# --------- |
| 57 | +# "~*\badultgalls\b" 1; |
| 58 | +# "~*\bamateurxpass\b" 1; |
| 59 | +# "~*\bbigblackbooty\b" 1; |
| 60 | +# "~*\bblacktits\b" 1; |
| 61 | +# "~*\bcookie\-law\-enforcement\b" 1; |
| 62 | +# "~*\bfree\-share\-buttons\b" 1; |
| 63 | +# "~*\bfree\-social\-buttons\b" 1; |
| 64 | +# "~*\bfuck\-paid\-share\-buttons\b" 1; |
| 65 | +# "~*\bilovevitaly\b" 1; |
| 66 | +# "~*\blaw\-enforcement\-bot\b" 1; |
| 67 | +# "~*\blaw\-enforcement\-check\b" 1; |
| 68 | +# "~*\bshare\-buttons\-for\-free\b" 1; |
| 69 | +# "~*\bwebfuck\b" 1; |
| 70 | +# "~*\bxxxrus\b" 1; |
| 71 | +# "~*\bzeroredirect\b" 1; |
| 72 | + |
| 73 | + "~*(?:\b)thisisabadword(?:\b|)" 1; |
| 74 | + "~*(?:\b)thisisanotherbadword(?:\b|)" 1; |
| 75 | + |
0 commit comments