Synchronet v3.17b-Win32 (install) has been released (Jan-2019).

New Synchronet YouTube channel

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 revision Previous revision
config:filter_files [2019/02/01 16:59]
digital man Not that leading white-space is now significant. Other minor edits.
config:filter_files [2019/02/07 19:22]
digital man Mention that C-style escapes are now supported. More examples.
Line 4: Line 4:
  
 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 =====
 +  * Leading white-space characters are ignored
   * Sequences of alphabetic letters are treated case-insensitively   * Sequences of alphabetic letters are treated case-insensitively
 +  * C-style string-literal backslash (''​\''​) [[wp>​C_syntax#​Strings|escape sequences]] are supported (as of v3.17c)
   * Sequences //​beginning//​ with an exclamation mark (''​!''​) negate the match logic for that sequence   * Sequences //​beginning//​ with an exclamation mark (''​!''​) negate the match logic for that sequence
   * 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
Line 16: Line 15:
   * All other sequences are "exact match" string comparisons   * All other sequences are "exact match" string comparisons
    
-Examples+==== Examples ​==== 
   * ''​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 "sysop the" or "​sysops"​. 
-  * ''​sysop~''​ would mean users could not use names that have the word "​sysop"​ anywhere in them, like "​imthesysop"​ or "Joe Sysop"​.+  * ''​sysop~''​ would mean users could not use names that have the word "​sysop" ​//anywhere// in them, like "​imthesysop"​ or "Joe Sysop"​.
  
-===== IPv4 CIDR Notation ​=====+=== Match strings with the character sequence "​viagra"​ anywhere within === 
 +  viagra~ 
 +   
 +=== Match strings beginning with the character sequence "​[adv]"​ === 
 +  [adv]* 
 + 
 +=== Match strings beginning with a space === 
 +  \ * 
 +   
 +=== Match the string "​administrator",​ exactly (but case-insensitively) === 
 +  administrator ​  
 +   
 +=== Match strings that do not begin with the character sequence: "the " === 
 +  !the * 
 + 
 +==== 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: 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:
Line 34: Line 47:
  
 IPv6 CIDR notation is not supported at this time. IPv6 CIDR notation is not supported at this time.
 + 
 ===== Trash Can Files ===== ===== Trash Can Files =====
  

In Other Languages