Synchronet v3.19b-Win32 (install) has been released (Jan-2022).

You can donate to the Synchronet project using PayPal.

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
config:filter_files [2017/02/09 22:21] – Document the new IPv4 CIDR notation support. digital manconfig:filter_files [2019/02/01 16:59] – Not that leading white-space is now significant. Other minor edits. digital man
Line 3: Line 3:
 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 =====
Line 10: Line 13:
   * 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
    
Line 17: Line 20:
   * ''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 ===== ===== IPv4 CIDR Notation =====
Line 27: Line 30:
  
 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). 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. IPv6 CIDR notation is not supported at this time.
Line 34: Line 39:
 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|
Line 57: Line 62:
  
 ^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'')|
Line 65: Line 70:
   * [[:config:|Configuration]]   * [[:config:|Configuration]]
  
-{{tag>filter abuse}}+{{tag>filter abuse spam}}