Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
config:filter_files [2016/10/17 14:58] – [Filter Exemption Files] Document ipfilter_exempt.cfg digital man | config:filter_files [2019/02/01 16:59] – Not that leading white-space is now significant. Other minor edits. digital man |
---|
Filter configuration (''[[dir:ctrl]]/*.cfg'') and trash can (''[[dir:text]]/*.can'') files allow the sysop to specify words (or any sequence of characters) that will be used to disallow clients, users, or their content. | Filter configuration (''[[dir:ctrl]]/*.cfg'') and trash can (''[[dir:text]]/*.can'') files allow the sysop to specify words (or any sequence of characters) that will be used to disallow clients, users, or their content. |
| |
Each line in a filter file may contain a comparison sequence. Blank lines and lines beginning with a semicolon are ignored | Each line in a filter file may contain a comparison sequence. Blank lines and lines beginning with a semicolon are ignored. |
| |
| **Note**: |
| Prior to v3.17c, leading white-space in filter file lines was ignored. As of v3.17c, leading white-space *is* significant and can be used for filters such " *" to filter (reject) any matches that begin with a leading space character. |
| |
===== Comparison Sequences ===== | ===== Comparison Sequences ===== |
* Sequences //beginning// with an asterisk (''*'') match only if the characters following the ''*'' are found at the end of the comparison string | * Sequences //beginning// with an asterisk (''*'') match only if the characters following the ''*'' are found at the end of the comparison string |
* Sequences //ending// with an asterisk (''*'') or caret (''^'') match only if the characters preceding are found at the beginning of the comparison string | * Sequences //ending// with an asterisk (''*'') or caret (''^'') match only if the characters preceding are found at the beginning of the comparison string |
* Sequences //ending// with a tilde (''~'') match only if the preceding characters are found anywhere within comparison string | * Sequences //ending// with a tilde (''~'') match when the preceding string of characters are found //anywhere// within the comparison string |
* All other sequences are "exact match" string comparisons | * All other sequences are "exact match" string comparisons |
| |
* ''sysop'' in the ''name.can'' file would mean users could not use the name "sysop". | * ''sysop'' in the ''name.can'' file would mean users could not use the name "sysop". |
* ''sysop*'' would mean users could not use names beginning with the word "sysop", like "sysopa" or "sysops" etc. | * ''sysop*'' would mean users could not use names beginning with the word "sysop", like "sysopa" or "sysops" etc. |
* ''sysop~'' would mean users could not use names that have the word "sysop" anywhere in them, like "imthesysop" or "mesysophere". | * ''sysop~'' would mean users could not use names that have the word "sysop" anywhere in them, like "imthesysop" or "Joe Sysop". |
| |
| ===== IPv4 CIDR Notation ===== |
| |
| An additional comparison format was introduced in v3.17 (Feb-9-2017) specifically for partial (ranges of) IPv4 address matching following standard [[wp>Classless_Inter-Domain_Routing]] (CIDR) notation. For example, rather than using the comparison string "192.168.1.*" to match all IP addresses that begin with the first 3 octets of 192, 168, and 1, you could specify the same thing using CIDR notation: |
| 192.168.1.0/24 |
| |
| This enables the flexibility of filtering ranges of IP addresses based on sub-networks that are not multiples of 8-bits (e.g. "192.168.1.33/30") and the format is compatible with commonly available regional block lists. |
| |
| All 4 octets of the IPv4 address must be specified in the CIDR comparison string (i.e. "192.168.1/24" is **not** a valid CIDR comparison string). |
| |
| CIDR comparisons beginning with the negation prefix (''!'') **are** supported (reverses the IP address comparison logic). |
| |
| IPv6 CIDR notation is not supported at this time. |
| |
===== Trash Can Files ===== | ===== Trash Can Files ===== |
The following table lists the supported trash can files, a description of their use, and optional rejection message (''.msg'') files that may be displayed to users that are (or have their content) filtered. Trash can files and their respective optional rejection message files are located in the ''[[dir:text]]'' directory: | The following table lists the supported trash can files, a description of their use, and optional rejection message (''.msg'') files that may be displayed to users that are (or have their content) filtered. Trash can files and their respective optional rejection message files are located in the ''[[dir:text]]'' directory: |
| |
^Filename / Page ^Default Contents^Rejection Message^Description^ | ^Filename / Page ^Default Contents^Rejection Message((Rejection message files are only used/displayed by the terminal server))^Description^ |
|''[[email.can]]'' |[[http://cvs.synchro.net/cgi-bin/viewcvs.cgi/*checkout*/text/email.can|email.can]]|''[[bademail.msg]]''|Disallowed (source or destination) e-mail addresses (see also ''[[twitlist.cfg]]'')| | |''[[email.can]]'' |[[http://cvs.synchro.net/cgi-bin/viewcvs.cgi/*checkout*/text/email.can|email.can]]|''[[bademail.msg]]''|Disallowed (source or destination) e-mail addresses (see also ''[[twitlist.cfg]]'')| |
|''[[file.can]]'' |[[http://cvs.synchro.net/cgi-bin/viewcvs.cgi/*checkout*/text/file.can|file.can]]|''[[badfile.msg]]''|Disallowed filenames for upload| | |''[[file.can]]'' |[[http://cvs.synchro.net/cgi-bin/viewcvs.cgi/*checkout*/text/file.can|file.can]]|''[[badfile.msg]]''|Disallowed filenames for upload| |
| |
^Filename / Page ^Default Contents^Description^ | ^Filename / Page ^Default Contents^Description^ |
|''[[ipfilter_exempt.cfg]]'' | | Hostnames and IP addresses that are considered exempt from temporary bans and permanent filtering (added Oct-17-2016)| | |''[[ipfilter_exempt.cfg]]'' |[[http://cvs.synchro.net/cgi-bin/viewcvs.cgi/*checkout*/ctrl/ipfilter_exempt.cfg|ipfilter_exempt.cfg]]| Hostnames and IP addresses that are considered exempt from temporary bans and permanent filtering (added Oct-17-2016)| |
|''[[dnsbl_exempt.cfg]]'' |[[http://cvs.synchro.net/cgi-bin/viewcvs.cgi/*checkout*/ctrl/dnsbl_exempt.cfg|dnsbl_exempt.cfg]]|Hostnames and IP addresses and e-mail address (enclosed in <angle brackets>) which are to be exempt from positive DNS-based Blacklist results in the [[server:mail|Mail Server]] (see also ''dns_blacklist.cfg'')| | |''[[dnsbl_exempt.cfg]]'' |[[http://cvs.synchro.net/cgi-bin/viewcvs.cgi/*checkout*/ctrl/dnsbl_exempt.cfg|dnsbl_exempt.cfg]]|Hostnames and IP addresses and e-mail address (enclosed in <angle brackets>) which are to be exempt from positive DNS-based Blacklist results in the [[server:mail|Mail Server]] (see also ''dns_blacklist.cfg'')| |
|''[[spamblock_exempt.cfg]]'' |[[http://cvs.synchro.net/cgi-bin/viewcvs.cgi/*checkout*/ctrl/spamblock_exempt.cfg|spamblock_exempt.cfg]]|Hostnames and IP addresses which are not to be blocked from sending e-mail to the [[server:mail|Mail Server]] (see also ''spamblock.cfg'')| | |''[[spamblock_exempt.cfg]]'' |[[http://cvs.synchro.net/cgi-bin/viewcvs.cgi/*checkout*/ctrl/spamblock_exempt.cfg|spamblock_exempt.cfg]]|Hostnames and IP addresses which are not to be blocked from sending e-mail to the [[server:mail|Mail Server]] (see also ''spamblock.cfg'')| |
* [[:config:|Configuration]] | * [[:config:|Configuration]] |
| |
{{tag>filter abuse}} | {{tag>filter abuse spam}} |
| |