DareNET IRCd Configuration/1.5 - Revision history

Nitemare: /* Connect block */

2013-06-17T18:00:33Z

Connect block

← Older revision		Revision as of 18:00, 17 June 2013
Line 279:		Line 279:
	*/</span>		*/</span>
	host = <span class="qstring">"192.168.0.1"</span>;		host = <span class="qstring">"192.168.0.1"</span>;
-
-	~~<span class="comment">/* vhost: (optional) the host or IP to bind to for this connection.~~
-	* If this is not specified, the default vhost (in general {}) is used.
-	*/</span>
-	~~<span class="comment">#vhost = "192.168.0.50";</span>~~

	<span class="comment">/* password: the password we send and accept. */</span>		<span class="comment">/* password: the password we send and accept. */</span>

Nitemare: Reverted edits by Nitemare (Talk) to last revision by Admin

2013-06-17T17:59:09Z

Reverted edits by Nitemare (Talk) to last revision by Admin

← Older revision		Revision as of 17:59, 17 June 2013
Line 49:		Line 49:
	*/</span>		*/</span>
	numeric = <span class="integer">999</span>;		numeric = <span class="integer">999</span>;
		+
		+	<span class="comment">/* vhost: the IP to bind to when we connect outward to other servers.
		+	* It must contain either a * or a valid ipv4 address in dotted quad notation.
		+	*/</span>
		+	vhost = <span class="qstring">"192.169.0.1"</span>;

	<span class="comment">/* ssl_private_key: our ssl private key. */</span>		<span class="comment">/* ssl_private_key: our ssl private key. */</span>
Line 827:		Line 832:
	* b (Bitmask DNSBL) - See your DNSBL provider as to whether you should use this or not.		* b (Bitmask DNSBL) - See your DNSBL provider as to whether you should use this or not.
	* r (Reply DNSBL) - See your DNSBL provider as to whether you should use this or not.		* r (Reply DNSBL) - See your DNSBL provider as to whether you should use this or not.
-	* a (Allow Connect) - Allow the client to connect anyway. This could used with a DNSBL whitelist. This could also be used to allow users to still connect, but mark their hosts so that channel ops can easily ban them from their channels. ~~(Bypass LOC requirements)~~	+	* a (Allow Connect) - Allow the client to connect anyway. This could used with a DNSBL whitelist. This could also be used to allow users to still connect, but mark their hosts so that channel ops can easily ban them from their channels.
	* d (Deny Connect) - If the user is found on this DNSBL, then they can't connect, even if they are allowed on through another DNSBL {} block.		* d (Deny Connect) - If the user is found on this DNSBL, then they can't connect, even if they are allowed on through another DNSBL {} block.
	* m (Mark Hostname) - Mark the hostname of a skipped client		* m (Mark Hostname) - Mark the hostname of a skipped client

Nitemare: /* General block */

2013-06-17T17:58:22Z

General block

← Older revision		Revision as of 17:58, 17 June 2013
Line 49:		Line 49:
	*/</span>		*/</span>
	numeric = <span class="integer">999</span>;		numeric = <span class="integer">999</span>;
-
-	~~<span class="comment">/* vhost: the IP to bind to when we connect outward to other servers.~~
-	* It must contain either a * or a valid ipv4 address in dotted quad notation.
-	*/</span>
-	~~vhost = <span class="qstring">"192.169.0.1"</span>;~~

	<span class="comment">/* ssl_private_key: our ssl private key. */</span>		<span class="comment">/* ssl_private_key: our ssl private key. */</span>

Nitemare: /* DNSBL Block */

2012-12-06T21:29:27Z

DNSBL Block

← Older revision		Revision as of 21:29, 6 December 2012
Line 832:		Line 832:
	* b (Bitmask DNSBL) - See your DNSBL provider as to whether you should use this or not.		* b (Bitmask DNSBL) - See your DNSBL provider as to whether you should use this or not.
	* r (Reply DNSBL) - See your DNSBL provider as to whether you should use this or not.		* r (Reply DNSBL) - See your DNSBL provider as to whether you should use this or not.
-	* a (Allow Connect) - Allow the client to connect anyway. This could used with a DNSBL whitelist. This could also be used to allow users to still connect, but mark their hosts so that channel ops can easily ban them from their channels.	+	* a (Allow Connect) - Allow the client to connect anyway. This could used with a DNSBL whitelist. This could also be used to allow users to still connect, but mark their hosts so that channel ops can easily ban them from their channels. (Bypass LOC requirements)
	* d (Deny Connect) - If the user is found on this DNSBL, then they can't connect, even if they are allowed on through another DNSBL {} block.		* d (Deny Connect) - If the user is found on this DNSBL, then they can't connect, even if they are allowed on through another DNSBL {} block.
	* m (Mark Hostname) - Mark the hostname of a skipped client		* m (Mark Hostname) - Mark the hostname of a skipped client

Admin at 07:06, 5 November 2012

2012-11-05T07:06:25Z

← Older revision		Revision as of 07:06, 5 November 2012
Line 2:		Line 2:
	This is a reference guide for ircd-darenet 1.5.x's configuration file.		This is a reference guide for ircd-darenet 1.5.x's configuration file.

-	The configuration format consists of various blocks, each containing name-value pairs, tags or string data. It is designed to be easily readable by both human ~~and~~ ircd.	+	The configuration format consists of various blocks, each containing name-value pairs, tags or string data. It is designed to be easily readable by both human ircd.

	A block consists of a name, an opening '{' brace, statements, a closing '}' brace, and a ';' semicolon. A statement consists of a name possibly followed by an '=' equals sign and a value, ending with a semicolon. All strings must be surrounded by '"' double quotes.		A block consists of a name, an opening '{' brace, statements, a closing '}' brace, and a ';' semicolon. A statement consists of a name possibly followed by an '=' equals sign and a value, ending with a semicolon. All strings must be surrounded by '"' double quotes.
Line 17:		Line 17:
	All elements of the configuration are separated by whitespace, and can be packed on one line, or broken up over several lines. Whitespace is defined as space, tab or carriage return/linefeed. Three forms of comments are allowed:		All elements of the configuration are separated by whitespace, and can be packed on one line, or broken up over several lines. Whitespace is defined as space, tab or carriage return/linefeed. Three forms of comments are allowed:

-	* C style single/multi-line	+	<pre>/* C style single/multi-line */
-	* ~~C++ style single-line~~	+
-	* Shell style single-line	+

-	'''Important:''' When the configuration file is parsed by the ircd, blocks are used in reverse order than how they are listed. This means you should start multiple block definitions with the "fall through", and end with the most detailed. Keep in mind that Class {} blocks must be specified before anything that uses them. That means they must be defined before Client {}, Connect {} and Operator {} blocks.	+	// C++ style single-line

-	~~Time~~ / ~~duration is written as:~~	+	# Shell style single-line
-	* A number in seconds (e.g., 60)	+	</pre>
-	* A grammatical expression (e.g., 1 hour 30 minutes 10 seconds)	+
-	* An arithmetic expression (e.g., 16020)	+

-	~~Valid units of time:~~	+	{{info\|text=Blocks are used in the reverse order than how they're listed, when the configuration file is parsed. This means you should start multiple block definitions with the "fall through", and end with the most detailed.}}
-	* decade / decades	+
-	* year / years	+
-	* month / months	+
-	* week / weeks	+
-	* day / days	+
-	* hour / hours	+
-	* minute / minutes	+
-	* second / seconds	+
-		+
-	~~Valid units of size:~~	+
-	* terabyte / terabytes / tbyte	+
-	* gigabyte / gigabytes / gbyte	+
-	* megabyte / megabytes / mbyte	+
-	* kilobyte / kilobytes / kbyte	+
-	* byte / bytes	+

	== General block ==		== General block ==

Nitemare: /* Except Block */

2012-11-04T01:19:01Z

Except Block

← Older revision		Revision as of 01:19, 4 November 2012
Line 688:		Line 688:

	NOTE: For throttling/clone exemptions (I), only IP addresses are supported, since these checks are performed before any DNS resolutions or identd replies are received.		NOTE: For throttling/clone exemptions (I), only IP addresses are supported, since these checks are performed before any DNS resolutions or identd replies are received.
		+	NOTE: For notilde (n), IP/Host is required.

	Example block:		Example block:

Nico: s/host/mask/ for Except

2012-10-15T17:16:24Z

s/host/mask/ for Except

← Older revision		Revision as of 17:16, 15 October 2012
Line 693:		Line 693:
	<c>Except		<c>Except
	{		{
-	~~host~~ = "@.darenet.org";	+	mask = "@.darenet.org";
	flags = "kgzsL";		flags = "kgzsL";
	};</c>		};</c>
Line 699:		Line 699:
	<c>Except		<c>Except
	{		{
-	~~host~~ = "*@127.0.0.1";	+	mask = "*@127.0.0.1";
	flags = "I";		flags = "I";
	};</c>		};</c>

Nitemare: /* Except Block */

2012-08-11T18:49:00Z

Except Block

← Older revision		Revision as of 18:49, 11 August 2012
Line 700:		Line 700:
	{		{
	host = "*@127.0.0.1";		host = "*@127.0.0.1";
-	flags = "T";	+	flags = "I";
	};</c>		};</c>

Admin: /* Operator block */

2012-08-10T06:18:00Z

Operator block

← Older revision		Revision as of 06:18, 10 August 2012
Line 467:		Line 467:
	</pre></html>		</pre></html>

-	The <code>name</code> and <code>password</code> ~~tokens~~ match the parameters of the <code>OPER</code> command. To authenticate as an ~~oper~~, a client must match one of the <code>host</code> ~~tokens specified in "user@host/IP mask" form. The host part is matched against both~~ resolved ~~hostnames and~~ IP address.	+	The <code>name</code> and <code>password</code> fields match the parameters of the <code>OPER</code> command. To authenticate as an IRC operator, a client must match one of the <code>host</code> fields, which may be a resolved hostname or IP address.

	To use an unencrypted password, prefix the password with '$PLAIN', e.g., "$PLAIN$aPpLe".		To use an unencrypted password, prefix the password with '$PLAIN', e.g., "$PLAIN$aPpLe".

-	If you want to use a more secure password authentication system, generate a 1024bit RSA key, and specify the path to the key as the password (as shown in the example above), and add 'R' to the flags field. This will use the <code>/CHALLENGE</code> system instead of <code>/OPER</code>. See doc/challenge.txt for more details.	+	If you want to use a more secure password authentication system, generate a 1024bit RSA key, and specify the path to the key as the password (as shown in the example above), and add 'R' to the <code>flags</code> field. This will use the <code>/CHALLENGE</code> system instead of <code>/OPER</code>. See doc/challenge.txt for more details.

-	~~An oper~~ may also use their SSL client certificate fingerprint to authenticate as an ~~oper~~. To use this method, specify the ~~oper~~'s certificate fingerprint as the password, and add 'S' to the flags field.	+	A client may also use their SSL client certificate fingerprint to authenticate as an IRC operator. To use this method, specify the client's certificate fingerprint as the password, and add 'S' to the <code>flags</code> field.

-	Only one password authentication method may be used at a time. That is, you cannot use CHALLENGE and SSL client certificate fingerprint at the same time.	+	Only one password authentication method may be used at a time. That is, you cannot use <code>CHALLENGE</code> and SSL client certificate fingerprint at the same time.

	There are currently 9 different oper flags:		There are currently 9 different oper flags:
Line 490:		Line 490:
	* j - Allowed to use juped nicknames.		* j - Allowed to use juped nicknames.

-	The class ~~token~~ specifies the connection class the ~~oper~~ will be placed in, regardless of their previous connection class. If not specified, the default class is used; see the Class block description for details.	+	The <code>class</code> field specifies the connection class the client will be placed in, regardless of their previous connection class. If not specified, the default class is used; see the Class block description for details.

	There may be multiple Operator blocks.		There may be multiple Operator blocks.

Admin: /* Port Block */

2012-08-10T06:13:32Z

Port Block

← Older revision		Revision as of 06:13, 10 August 2012
Line 413:		Line 413:
	</pre></html>		</pre></html>

-	The mask ~~setting~~ should only contain IP addresses or '' if used. This does not use DNS in any way, so you cannot use it to allow .nl or .uk, for example. Attempting to specify anything other than IP addresses will result in the port allowing connections from anyone (as if you used '').	+	The <code>mask</code> field should only contain IP addresses (CIDR notation is supported) or '', if used. This does not use DNS in any way, so you cannot use it to allow .dk or .uk, for example. Attempting to specify anything other than IP addresses will result in the port allowing connections from anyone (as if you used '').

-	If a bind address ~~(vhost~~) is not specified, the server will listen on all available interfaces for that port.	+	If the <code>vhost</code> field (i.e., bind address) is not specified, the server will listen on all available interfaces for that port.

	There may be multiple Port blocks.		There may be multiple Port blocks.