doc/sgml/oper-guide/config.sgml

   1   <chapter id="config">
   2     <title>Server config file format</title>
   3     <sect1>
   4       <title>General format</title>
   5       <para>
   6         The config file consists of a series of BIND-style blocks. Each block consists of a series
   7         of values inside it which pertain to configuration settings that apply to the given block.
   8       </para>
   9       <para>
  10         Several values take lists of values and have defaults preset inside
  11         them. Prefix a keyword with a tilde (~) to override the default and
  12         disable it.
  13       </para>
  14       <para>
  15         A line may also be a .include directive, which is of the form <synopsis>.include "<replaceable>file</replaceable>"</synopsis>
  16         and causes <replaceable>file</replaceable> to be read in at that point, before the rest of the current file is
  17         processed.
  18         Relative paths are first tried relative to PREFIX and then relative
  19         to ETCPATH (normally PREFIX/etc).
  20       </para>
  21       <para>
  22         Anything from a # to the end of a line is a comment. Blank lines are ignored. C-style comments are also supported.
  23       </para>
  24     </sect1>
  25     <sect1 id="configlines">
  26       <title>Specific blocks and directives</title>
  27       <para>
  28         Not all configuration blocks and directives are listed here, only the most common ones. More blocks and directives will
  29         be documented in later revisions of this manual.
  30       </para>
  31       <sect2>
  32         <title>loadmodule directive</title>
  33         <synopsis>
  34 loadmodule "<replaceable>text</replaceable>";</synopsis>
  35         <para>
  36           Loads a module into the IRCd. In charybdis 1.1, most modules are automatically loaded in. In future versions, it is
  37           intended to remove this behaviour as to allow for easy customization of the IRCd's featureset.
  38         </para>
  39       </sect2>
  40       <sect2>
  41         <title>serverinfo {} block</title>
  42         <synopsis>
  43 serverinfo {
  44         name = "<replaceable>text</replaceable>";
  45         use_ts6 = <replaceable>boolean</replaceable>;
  46         sid = "<replaceable>text</replaceable>";
  47         description = "<replaceable>text</replaceable>";
  48         network_name = "<replaceable>text</replaceable>";
  49         network_desc = "<replaceable>text</replaceable>";
  50         hub = <replaceable>boolean</replaceable>;
  51         vhost = "<replaceable>text</replaceable>";
  52         vhost6 = "<replaceable>text</replaceable>";
  53 };</synopsis>
  54         <para>
  55           The serverinfo {} block defines the core operational parameters of the IRC server.
  56         </para>
  57         <variablelist>
  58           <title>serverinfo {} variables</title>
  59           <varlistentry>
  60             <term>name</term>
  61             <listitem>
  62               <para>
  63                 The name of the IRC server that you are configuring. This
  64                 must contain at least one dot. It is not necessarily equal
  65                 to any DNS name. This must be unique on the IRC network.
  66               </para>
  67             </listitem>
  68           </varlistentry>
  69           <varlistentry>
  70             <term>use_ts6</term>
  71             <listitem>
  72               <para>
  73                 A boolean which defines whether or not you want to use the new TS6 protocol, which provides
  74                 many improvements over the old protocol, TS5, which is used in Hyperion.
  75               </para>
  76             </listitem>
  77           </varlistentry>
  78           <varlistentry>
  79             <term>sid</term>
  80             <listitem>
  81               <para>
  82                 A unique ID which describes the server. This is required regardless of whether you are using
  83                 TS6 or not.
  84                 This consists of one digit and two characters which can be
  85                 digits or letters.
  86               </para>
  87             </listitem>
  88           </varlistentry>
  89           <varlistentry>
  90             <term>description</term>
  91             <listitem>
  92               <para>
  93                 A user-defined field of text which describes the IRC server. This information is used in
  94                 /links and /whois requests. Geographical location information could be a useful use of
  95                 this field, but most administrators put a witty saying inside it instead.
  96               </para>
  97             </listitem>
  98           </varlistentry>
  99           <varlistentry>
 100             <term>network_name</term>
 101             <listitem>
 102               <para>
 103                 The name of the IRC network that this server will be a member of.
 104                 This is used in the welcome message and NETWORK= in 005.
 105               </para>
 106             </listitem>
 107           </varlistentry>
 108           <varlistentry>
 109             <term>network_desc</term>
 110             <listitem>
 111               <para>
 112                 A description of the IRC network that this server will be a member of.
 113                 This is currently unused.
 114               </para>
 115             </listitem>
 116           </varlistentry>
 117           <varlistentry>
 118             <term>hub</term>
 119             <listitem>
 120               <para>
 121                 A boolean which defines whether or not this IRC server will be serving as a hub, i.e. have multiple servers connected to it.
 122               </para>
 123             </listitem>
 124           </varlistentry>
 125           <varlistentry>
 126             <term>vhost</term>
 127             <listitem>
 128               <para>
 129                 An optional text field which defines an IP from which to connect outward to other IRC servers.
 130               </para>
 131             </listitem>
 132           </varlistentry>
 133           <varlistentry>
 134             <term>vhost6</term>
 135             <listitem>
 136               <para>
 137                 An optional text field which defines an IPv6 IP from which to connect outward to other IRC servers.
 138               </para>
 139             </listitem>
 140           </varlistentry>
 141         </variablelist>
 142       </sect2>
 143       <sect2>
 144         <title>admin {} block</title>
 145         <synopsis>
 146 admin {
 147         name = "<replaceable>text</replaceable>";
 148         description = "<replaceable>text</replaceable>";
 149         email = "<replaceable>text</replaceable>";
 150 };</synopsis>
 151         <para>
 152           This block provides the information which is returned by the ADMIN command.
 153         </para>
 154         <variablelist>
 155           <title>admin {} variables</title>
 156           <varlistentry>
 157             <term>name</term>
 158             <listitem>
 159               <para>The name of the administrator running this service.</para>
 160             </listitem>
 161           </varlistentry>
 162           <varlistentry>
 163             <term>description</term>
 164             <listitem>
 165               <para>The description of the administrator's position in the network.</para>
 166             </listitem>
 167           </varlistentry>
 168           <varlistentry>
 169             <term>email</term>
 170             <listitem>
 171               <para>A point of contact for the administrator, usually an e-mail address.</para>
 172             </listitem>
 173           </varlistentry>
 174         </variablelist>
 175       </sect2>
 176       <sect2>
 177         <title>class {} block</title>
 178         <synopsis>
 179 class "<replaceable>name</replaceable>" {
 180         ping_time = <replaceable>duration</replaceable>;
 181         number_per_ident = <replaceable>number</replaceable>;
 182         number_per_ip = <replaceable>number</replaceable>;
 183         number_per_ip_global = <replaceable>number</replaceable>;
 184         cidr_bitlen = <replaceable>number</replaceable>;
 185         number_per_cidr = <replaceable>number</replaceable>;
 186         max_number = <replaceable>number</replaceable>;
 187         sendq = <replaceable>size</replaceable>;
 188 };</synopsis>
 189         <synopsis>
 190 class "<replaceable>name</replaceable>" {
 191         ping_time = <replaceable>duration</replaceable>;
 192         connectfreq = <replaceable>duration</replaceable>;
 193         max_number = <replaceable>number</replaceable>;
 194         sendq = <replaceable>size</replaceable>;
 195 };</synopsis>
 196         <para>
 197           Class blocks define classes of connections for later use.
 198           The class name is used to connect them to
 199           other blocks in the config file (auth{} and connect{}).
 200           They must be defined before they are used.
 201         </para>
 202         <para>
 203           Classes are used both for client and server connections,
 204           but most variables are different.
 205         </para>
 206         <variablelist>
 207           <title>class {} variables: client classes</title>
 208           <varlistentry>
 209             <term>ping_time</term>
 210             <listitem>
 211               <para>The amount of time between checking pings for clients, e.g.: 2 minutes</para>
 212             </listitem>
 213           </varlistentry>
 214           <varlistentry>
 215             <term>number_per_ident</term>
 216             <listitem>
 217               <para>The amount of clients which may be connected from a single identd username on a per-IP basis, globally. Unidented clients all count as the same username.</para>
 218             </listitem>
 219           </varlistentry>
 220           <varlistentry>
 221             <term>number_per_ip</term>
 222             <listitem>
 223               <para>The amount of clients which may be connected from a single IP address.</para>
 224             </listitem>
 225           </varlistentry>
 226           <varlistentry>
 227             <term>number_per_ip_global</term>
 228             <listitem>
 229               <para>The amount of clients which may be connected globally from a single IP address.</para>
 230             </listitem>
 231           </varlistentry>
 232           <varlistentry>
 233             <term>cidr_bitlen</term>
 234             <listitem>
 235               <para>The netblock length to use with CIDR-based client limiting for this class.</para>
 236             </listitem>
 237           </varlistentry>
 238           <varlistentry>
 239             <term>number_per_cidr</term>
 240             <listitem>
 241               <para>The amount of clients which may be connected from a single netblock.</para>
 242             </listitem>
 243           </varlistentry>
 244           <varlistentry>
 245             <term>max_number</term>
 246             <listitem>
 247               <para>The maximum amount of clients which may use this class at any given time.</para>
 248             </listitem>
 249           </varlistentry>
 250           <varlistentry>
 251             <term>sendq</term>
 252             <listitem>
 253               <para>The maximum size of the queue of data to be sent to a client before it is dropped.</para>
 254             </listitem>
 255           </varlistentry>
 256         </variablelist>
 257         <variablelist>
 258           <title>class {} variables: server classes</title>
 259           <varlistentry>
 260             <term>ping_time</term>
 261             <listitem>
 262               <para>The amount of time between checking pings for servers, e.g.: 2 minutes</para>
 263             </listitem>
 264           </varlistentry>
 265           <varlistentry>
 266             <term>connectfreq</term>
 267             <listitem>
 268               <para>The amount of time between autoconnects. This must at least be one minute, as autoconnects are evaluated with that granularity.</para>
 269             </listitem>
 270           </varlistentry>
 271           <varlistentry>
 272             <term>max_number</term>
 273             <listitem>
 274               <para>The amount of servers to autoconnect to in this class. More precisely, no autoconnects are done if the number of servers in this class is greater than or equal max_number</para>
 275             </listitem>
 276           </varlistentry>
 277           <varlistentry>
 278             <term>sendq</term>
 279             <listitem>
 280               <para>The maximum size of the queue of data to be sent to a server before it is dropped.</para>
 281             </listitem>
 282           </varlistentry>
 283         </variablelist>
 284       </sect2>
 285       <sect2>
 286         <title>auth {} block</title>
 287         <synopsis>
 288 auth {
 289         user = "<replaceable>hostmask</replaceable>";
 290         password = "<replaceable>text</replaceable>";
 291         spoof = "<replaceable>text</replaceable>";
 292         flags = <replaceable>list</replaceable>;
 293         class = "<replaceable>text</replaceable>";
 294 };</synopsis>
 295         <para>
 296           auth {} blocks allow client connections to the server, and set various properties concerning those connections.
 297         </para>
 298         <para>
 299           Auth blocks are evaluated from top to bottom in priority, so put special blocks first.
 300         </para>
 301         <variablelist>
 302           <title>auth {} variables</title>
 303           <varlistentry>
 304             <term>user</term>
 305             <listitem>
 306               <para>A hostmask (user@host) that the auth{} block is matched against. You can have multiple user entries.</para>
 307             </listitem>
 308           </varlistentry>
 309           <varlistentry>
 310             <term>password</term>
 311             <listitem>
 312               <para>
 313                 An optional password to use for authenticating into this auth{}
 314                 block.  If the password is wrong the user will not be able to
 315                 connect (will not fall back on another auth{} block).
 316               </para>
 317             </listitem>
 318           </varlistentry>
 319           <varlistentry>
 320             <term>spoof</term>
 321             <listitem>
 322               <para>An optional fake hostname (or user@host) to apply to users authenticated to this auth{} block.</para>
 323             </listitem>
 324           </varlistentry>
 325           <varlistentry>
 326             <term>flags</term>
 327             <listitem>
 328               <para>A list of flags to apply to this auth{} block. They are listed below.</para>
 329             </listitem>
 330           </varlistentry>
 331           <varlistentry>
 332             <term>class</term>
 333             <listitem>
 334               <para>A name of a class to put users matching this auth{} block into.</para>
 335             </listitem>
 336           </varlistentry>
 337         </variablelist>
 338         <variablelist>
 339           <title>auth {} flags</title>
 340           <varlistentry>
 341             <term>encrypted</term>
 342             <listitem>
 343               <para>The password used has been encrypted.</para>
 344             </listitem>
 345           </varlistentry>
 346           <varlistentry>
 347             <term>spoof_notice</term>
 348             <listitem>
 349               <para>Causes the IRCd to send out a server notice when activating a spoof provided by this auth{} block.</para>
 350             </listitem>
 351           </varlistentry>
 352           <varlistentry>
 353             <term>exceed_limit</term>
 354             <listitem>
 355               <para>Users in this auth{} block can exceed class-wide limitations.</para>
 356             </listitem>
 357           </varlistentry>
 358           <varlistentry>
 359             <term>dnsbl_exempt</term>
 360             <listitem>
 361               <para>Users in this auth{} block are exempted from DNS blacklist checks. However, they will still be warned if they are listed.</para>
 362             </listitem>
 363           </varlistentry>
 364           <varlistentry>
 365             <term>kline_exempt</term>
 366             <listitem>
 367               <para>Users in this auth{} block are exempted from DNS blacklists, k:lines, g:lines and x:lines, and will not be disconnected because of d:lines.</para>
 368             </listitem>
 369           </varlistentry>
 370           <varlistentry>
 371             <term>gline_exempt</term>
 372             <listitem>
 373               <para>Users in this auth{} block are exempted from g:lines.</para>
 374             </listitem>
 375           </varlistentry>
 376           <varlistentry>
 377             <term>spambot_exempt</term>
 378             <listitem>
 379               <para>Users in this auth{} block are exempted from spambot checks.</para>
 380             </listitem>
 381           </varlistentry>
 382           <varlistentry>
 383             <term>shide_exempt</term>
 384             <listitem>
 385               <para>Users in this auth{} block are exempted from some serverhiding effects.</para>
 386             </listitem>
 387           </varlistentry>
 388           <varlistentry>
 389             <term>jupe_exempt</term>
 390             <listitem>
 391               <para>Users in this auth{} block do not trigger an alarm when joining juped channels.</para>
 392             </listitem>
 393           </varlistentry>
 394           <varlistentry>
 395             <term>resv_exempt</term>
 396             <listitem>
 397               <para>Users in this auth{} block may use reserved nicknames and channels.</para>
 398               <note><para>The initial nickname may still not be reserved.</para></note>
 399             </listitem>
 400           </varlistentry>
 401           <varlistentry>
 402             <term>flood_exempt</term>
 403             <listitem>
 404               <para>
 405                 Users in this auth{} block may send arbitrary amounts of
 406                 commands per time unit to the server. This does not exempt
 407                 them from any other flood limits.
 408                 You should use this setting with caution.
 409               </para>
 410             </listitem>
 411           </varlistentry>
 412           <varlistentry>
 413             <term>no_tilde</term>
 414             <listitem>
 415               <para>Users in this auth{} block will not have a tilde added to their username if they do not run identd.</para>
 416             </listitem>
 417           </varlistentry>
 418           <varlistentry>
 419             <term>need_ident</term>
 420             <listitem>
 421               <para>Users in this auth{} block must have identd, otherwise they will be rejected.</para>
 422             </listitem>
 423           </varlistentry>
 424           <varlistentry>
 425             <term>need_sasl</term>
 426             <listitem>
 427               <para>Users in this auth{} block must identify via SASL, otherwise they will be rejected.</para>
 428             </listitem>
 429           </varlistentry>
 430         </variablelist>
 431       </sect2>
 432       <sect2>
 433         <title>exempt {} block</title>
 434         <synopsis>
 435 exempt {
 436         ip = "<replaceable>ip</replaceable>";
 437 };</synopsis>
 438         <para>
 439           An exempt block specifies IP addresses which are exempt from D:lines.
 440           Multiple addresses can be specified in one block.
 441           Clients coming from these addresses can still be K/G/X:lined or
 442           banned by a DNS blacklist unless
 443           they also have appropriate flags in their auth{} block.
 444         </para>
 445         <variablelist>
 446           <title>exempt {} variables</title>
 447           <varlistentry>
 448             <term>ip</term>
 449             <listitem>
 450               <para>The IP address or CIDR range to exempt.</para>
 451             </listitem>
 452           </varlistentry>
 453         </variablelist>
 454       </sect2>
 455       <sect2>
 456         <title>operator {} block</title>
 457         <synopsis>
 458 operator "<replaceable>name</replaceable>" {
 459         user = "<replaceable>hostmask</replaceable>";
 460         password = "<replaceable>text</replaceable>";
 461         rsa_public_key_file = "<replaceable>text</replaceable>";
 462         umodes = <replaceable>list</replaceable>;
 463         snomask = "<replaceable>text</replaceable>";
 464         flags = <replaceable>list</replaceable>;
 465 };</synopsis>
 466         <para>
 467           Operator blocks define who may use the OPER command to gain extended privileges.
 468         </para>
 469         <variablelist>
 470           <title>operator {} variables</title>
 471           <varlistentry>
 472             <term>user</term>
 473             <listitem>
 474               <para>
 475                 A hostmask that users trying to use this operator {} block
 476                 must match. This is checked against the original host and IP
 477                 address; CIDR is also supported. So auth {} spoofs work in
 478                 operator {} blocks; the real host behind them is not checked.
 479                 Other kind of spoofs do not work in operator {} blocks; the
 480                 real host behind them is checked.
 481               </para>
 482               <para>
 483                 Note that this is different from charybdis 1.x where all
 484                 kinds of spoofs worked in operator {} blocks.
 485               </para>
 486             </listitem>
 487           </varlistentry>
 488           <varlistentry>
 489             <term>password</term>
 490             <listitem>
 491               <para>
 492                 A password used with the OPER command to use this operator {} block.
 493                 Passwords are encrypted by default, but may be unencrypted if ~encrypted is present
 494                 in the flags list.
 495               </para>
 496             </listitem>
 497           </varlistentry>
 498           <varlistentry>
 499             <term>rsa_public_key_file</term>
 500             <listitem>
 501               <para>
 502                 An optional path to a RSA public key file associated with the operator {} block.
 503                 This information is used by the CHALLENGE command, which is an alternative authentication
 504                 scheme to the traditional OPER command.
 505               </para>
 506             </listitem>
 507           </varlistentry>
 508           <varlistentry>
 509             <term>umodes</term>
 510             <listitem>
 511               <para>A list of usermodes to apply to successfully opered clients.</para>
 512             </listitem>
 513           </varlistentry>
 514           <varlistentry>
 515             <term>snomask</term>
 516             <listitem>
 517               <para>
 518                 An snomask to apply to successfully opered clients.
 519               </para>
 520             </listitem>
 521           </varlistentry>
 522           <varlistentry>
 523             <term>flags</term>
 524             <listitem>
 525               <para>
 526                 A listing of privileges granted to operators using this block.
 527                 By default, the operwall and remoteban privileges are granted;
 528                 use ~operwall and ~remoteban to disable them if necessary.
 529               </para>
 530               <para>
 531                 In addition, a flag designating if the password is encrypted is here.
 532                 Privileges are documented elsewhere in this guide.
 533               </para>
 534             </listitem>
 535           </varlistentry>
 536         </variablelist>
 537       </sect2>
 538       <sect2>
 539         <title>connect {} block</title>
 540         <synopsis>
 541 connect "<replaceable>name</replaceable>" {
 542         host = "<replaceable>text</replaceable>";
 543         send_password = "<replaceable>text</replaceable>";
 544         accept_password = "<replaceable>text</replaceable>";
 545         port = <replaceable>number</replaceable>;
 546         hub_mask = "<replaceable>mask</replaceable>";
 547         leaf_mask = "<replaceable>mask</replaceable>";
 548         class = "<replaceable>text</replaceable>";
 549         flags = <replaceable>list</replaceable>;
 550         aftype = <replaceable>protocol</replaceable>;
 551 };</synopsis>
 552         <para>
 553           Connect blocks define what servers may connect or be connected to.
 554         </para>
 555         <variablelist>
 556           <title>connect {} variables</title>
 557           <varlistentry>
 558             <term>host</term>
 559             <listitem>
 560               <para>The hostname or IP to connect to.</para>
 561               <note><para>
 562                 Charybdis uses solely DNS for all hostname/address lookups
 563                 (no <filename>/etc/hosts</filename> or anything else).
 564                 Furthermore, if a hostname is used, it must have an A or AAAA
 565                 record (no CNAME) and it must be the primary
 566                 hostname for inbound connections to work.
 567               </para></note>
 568             </listitem>
 569           </varlistentry>
 570           <varlistentry>
 571             <term>send_password</term>
 572             <listitem>
 573               <para>The password to send to the other server.</para>
 574             </listitem>
 575           </varlistentry>
 576           <varlistentry>
 577             <term>accept_password</term>
 578             <listitem>
 579               <para>The password that should be accepted from the other server.</para>
 580             </listitem>
 581           </varlistentry>
 582           <varlistentry>
 583             <term>port</term>
 584             <listitem>
 585               <para>The port on the other server to connect to.</para>
 586             </listitem>
 587           </varlistentry>
 588           <varlistentry>
 589             <term>hub_mask</term>
 590             <listitem>
 591               <para>
 592                 An optional domain mask of servers allowed to be introduced
 593                 by this link. Usually, "*" is fine. Multiple hub_masks may be
 594                 specified, and any of them may be introduced.
 595                 Violation of hub_mask and leaf_mask restrictions will
 596                 cause the local link to be closed.
 597               </para>
 598             </listitem>
 599           </varlistentry>
 600           <varlistentry>
 601             <term>leaf_mask</term>
 602             <listitem>
 603               <para>
 604                 An optional domain mask of servers not allowed to be
 605                 introduced by this link. Multiple leaf_masks may be specified,
 606                 and none of them may be introduced. leaf_mask has priority
 607                 over hub_mask.
 608               </para>
 609             </listitem>
 610           </varlistentry>
 611           <varlistentry>
 612             <term>class</term>
 613             <listitem>
 614               <para>The name of the class this server should be placed into.</para>
 615             </listitem>
 616           </varlistentry>
 617           <varlistentry>
 618             <term>flags</term>
 619             <listitem>
 620               <para>A list of flags concerning the connect block. They are listed below.</para>
 621             </listitem>
 622           </varlistentry>
 623           <varlistentry>
 624             <term>aftype</term>
 625             <listitem>
 626               <para>The protocol that should be used to connect with, either ipv4 or ipv6. This defaults to ipv4 unless host is a numeric IPv6 address.</para>
 627             </listitem>
 628           </varlistentry>
 629         </variablelist>
 630         <variablelist>
 631           <title>connect {} flags</title>
 632           <varlistentry>
 633             <term>encrypted</term>
 634             <listitem>
 635               <para>The value for accept_password has been encrypted.</para>
 636             </listitem>
 637           </varlistentry>
 638           <varlistentry>
 639             <term>autoconn</term>
 640             <listitem>
 641               <para>
 642                 The server should automatically try to connect to the server defined in this
 643                 connect {} block if it's not connected already and max_number
 644                 in the class is not reached yet.
 645               </para>
 646             </listitem>
 647           </varlistentry>
 648           <varlistentry>
 649             <term>compressed</term>
 650             <listitem>
 651               <para>Ziplinks should be used with this server connection.
 652               This compresses traffic using zlib, saving some bandwidth
 653               and speeding up netbursts.</para>
 654               <para>If you have trouble setting up a link, you should
 655               turn this off as it often hides error messages.</para>
 656             </listitem>
 657           </varlistentry>
 658           <varlistentry>
 659             <term>topicburst</term>
 660             <listitem>
 661               <para>Topics should be bursted to this server.</para>
 662             </listitem>
 663           </varlistentry>
 664         </variablelist>
 665       </sect2>
 666       <sect2>
 667         <title>listen {} block</title>
 668         <synopsis>
 669 listen {
 670         host = "<replaceable>text</replaceable>";
 671         port = <replaceable>number</replaceable>;
 672 };</synopsis>
 673         <para>
 674           A listen block specifies what ports a server should listen on.
 675         </para>
 676         <variablelist>
 677           <title>listen {} variables</title>
 678           <varlistentry>
 679             <term>host</term>
 680             <listitem>
 681               <para>An optional host to bind to. Otherwise, the ircd will listen on all available hosts.</para>
 682             </listitem>
 683           </varlistentry>
 684           <varlistentry>
 685             <term>port</term>
 686             <listitem>
 687               <para>
 688                 A port to listen on. You can specify multiple ports via commas, and define a range by seperating
 689                 the start and end ports with two dots (..).
 690               </para>
 691             </listitem>
 692           </varlistentry>
 693         </variablelist>
 694       </sect2>
 695       <sect2>
 696         <title>modules {} block</title>
 697         <synopsis>
 698 modules {
 699         path = "<replaceable>text</replaceable>";
 700         module = <replaceable>text</replaceable>;
 701 };</synopsis>
 702         <para>
 703           The modules block specifies information for loadable modules.
 704         </para>
 705         <variablelist>
 706           <title>modules {} variables</title>
 707           <varlistentry>
 708             <term>path</term>
 709             <listitem>
 710               <para>Specifies a path to search for loadable modules.</para>
 711             </listitem>
 712           </varlistentry>
 713           <varlistentry>
 714             <term>module</term>
 715             <listitem>
 716               <para>
 717                 Specifies a module to load, similar to loadmodule.
 718               </para>
 719             </listitem>
 720           </varlistentry>
 721         </variablelist>
 722       </sect2>
 723       <sect2>
 724         <title>general {} block</title>
 725         <synopsis>
 726 modules {
 727         <replaceable>values</replaceable>
 728 };</synopsis>
 729         <para>
 730           The general block specifies a variety of options, many of which
 731           were in <filename>config.h</filename> in older daemons.
 732           The options are documented in <filename>reference.conf</filename>.
 733         </para>
 734       </sect2>
 735       <sect2>
 736         <title>channel {} block</title>
 737         <synopsis>
 738 modules {
 739         <replaceable>values</replaceable>
 740 };</synopsis>
 741         <para>
 742           The channel block specifies a variety of channel-related options,
 743           many of which were in <filename>config.h</filename> in older daemons.
 744           The options are documented in <filename>reference.conf</filename>.
 745         </para>
 746       </sect2>
 747       <sect2>
 748         <title>serverhide {} block</title>
 749         <synopsis>
 750 modules {
 751         <replaceable>values</replaceable>
 752 };</synopsis>
 753         <para>
 754           The serverhide block specifies options related to server hiding.
 755           The options are documented in <filename>reference.conf</filename>.
 756         </para>
 757       </sect2>
 758       <sect2>
 759         <title>blacklist {} block</title>
 760         <synopsis>
 761 blacklist {
 762         host = "<replaceable>text</replaceable>";
 763         reject_reason = "<replaceable>text</replaceable>";
 764 };</synopsis>
 765         <para>
 766           The blacklist block specifies DNS blacklists to check.
 767           Listed clients will not be allowed to connect.
 768           IPv6 clients are not checked against these.
 769         </para>
 770         <para>
 771           Multiple blacklists can be specified, in pairs with first host
 772           then reject_reason.
 773         </para>
 774         <variablelist>
 775           <title>blacklist {} variables</title>
 776           <varlistentry>
 777             <term>host</term>
 778             <listitem>
 779               <para>The DNSBL to use.</para>
 780             </listitem>
 781           </varlistentry>
 782           <varlistentry>
 783             <term>reject_reason</term>
 784             <listitem>
 785               <para>The reason to send to listed clients when disconnecting them.</para>
 786             </listitem>
 787           </varlistentry>
 788         </variablelist>
 789       </sect2>
 790       <sect2>
 791         <title>alias {} block</title>
 792         <synopsis>
 793 alias "<replaceable>name</replaceable>" {
 794         target = "<replaceable>text</replaceable>";
 795 };</synopsis>
 796         <para>
 797           Alias blocks allow the definition of custom commands.
 798           These commands send PRIVMSG to the given target. A real
 799           command takes precedence above an alias.
 800         </para>
 801         <variablelist>
 802           <title>alias {} variables</title>
 803           <varlistentry>
 804             <term>target</term>
 805             <listitem>
 806               <para>
 807                 The target nick (must be a network service (umode +S)) or
 808                 user@server.
 809                 In the latter case, the server cannot be this server,
 810                 only opers can use user starting with "opers" reliably and
 811                 the user is interpreted on the target server only
 812                 so you may need to use nick@server instead).
 813               </para>
 814             </listitem>
 815           </varlistentry>
 816         </variablelist>
 817       </sect2>
 818       <sect2>
 819         <title>cluster {} block</title>
 820         <synopsis>
 821 cluster {
 822         name = "<replaceable>text</replaceable>";
 823         flags = <replaceable>list</replaceable>;
 824 };</synopsis>
 825         <para>
 826           The cluster block specifies servers we propagate things to
 827           automatically.
 828           This does not allow them to set bans, you need a separate shared{}
 829           block for that.
 830         </para>
 831         <para>
 832           Having overlapping cluster{} items will cause the command to
 833           be executed twice on the target servers. This is particularly
 834           undesirable for ban removals.
 835         </para>
 836         <para>
 837           The letters in parentheses denote the flags in /stats U.
 838         </para>
 839         <variablelist>
 840           <title>cluster {} variables</title>
 841           <varlistentry>
 842             <term>name</term>
 843             <listitem>
 844               <para>The server name to share with, this may contain wildcards
 845               and may be stacked.</para>
 846             </listitem>
 847           </varlistentry>
 848           <varlistentry>
 849             <term>flags</term>
 850             <listitem>
 851               <para>The list of what to share, all the name lines above this
 852               (up to another flags entry) will receive these flags.
 853               They are listed below.</para>
 854             </listitem>
 855           </varlistentry>
 856         </variablelist>
 857         <variablelist>
 858           <title>cluster {} flags</title>
 859           <varlistentry>
 860             <term>kline (K)</term>
 861             <listitem>
 862               <para>Permanent K:lines</para>
 863             </listitem>
 864           </varlistentry>
 865           <varlistentry>
 866             <term>tkline (k)</term>
 867             <listitem>
 868               <para>Temporary K:lines</para>
 869             </listitem>
 870           </varlistentry>
 871           <varlistentry>
 872             <term>unkline (U)</term>
 873             <listitem>
 874               <para>K:line removals</para>
 875             </listitem>
 876           </varlistentry>
 877           <varlistentry>
 878             <term>xline (X)</term>
 879             <listitem>
 880               <para>Permanent X:lines</para>
 881             </listitem>
 882           </varlistentry>
 883           <varlistentry>
 884             <term>txline (x)</term>
 885             <listitem>
 886               <para>Temporary X:lines</para>
 887             </listitem>
 888           </varlistentry>
 889           <varlistentry>
 890             <term>unxline (Y)</term>
 891             <listitem>
 892               <para>X:line removals</para>
 893             </listitem>
 894           </varlistentry>
 895           <varlistentry>
 896             <term>resv (Q)</term>
 897             <listitem>
 898               <para>Permanently reserved nicks/channels</para>
 899             </listitem>
 900           </varlistentry>
 901           <varlistentry>
 902             <term>tresv (q)</term>
 903             <listitem>
 904               <para>Temporarily reserved nicks/channels</para>
 905             </listitem>
 906           </varlistentry>
 907           <varlistentry>
 908             <term>unresv (R)</term>
 909             <listitem>
 910               <para>RESV removals</para>
 911             </listitem>
 912           </varlistentry>
 913           <varlistentry>
 914             <term>locops (L)</term>
 915             <listitem>
 916               <para>LOCOPS messages (sharing this with * makes LOCOPS rather
 917               similar to OPERWALL which is not useful)</para>
 918             </listitem>
 919           </varlistentry>
 920           <varlistentry>
 921             <term>all</term>
 922             <listitem>
 923               <para>All of the above</para>
 924             </listitem>
 925           </varlistentry>
 926         </variablelist>
 927       </sect2>
 928       <sect2>
 929         <title>shared {} block</title>
 930         <synopsis>
 931 shared {
 932         oper = "<replaceable>user@host</replaceable>", "<replaceable>server</replaceable>";
 933         flags = <replaceable>list</replaceable>;
 934 };</synopsis>
 935         <para>
 936           The shared block specifies opers allowed to perform certain actions
 937           on our server remotely.
 938           These are ordered top down. The first one matching will determine
 939           the oper's access.
 940           If access is denied, the command will be silently ignored.
 941         </para>
 942         <para>
 943           The letters in parentheses denote the flags in /stats U.
 944         </para>
 945         <variablelist>
 946           <title>shared {} variables</title>
 947           <varlistentry>
 948             <term>oper</term>
 949             <listitem>
 950               <para>The user@host the oper must have, and the server they must
 951               be on. This may contain wildcards.</para>
 952             </listitem>
 953           </varlistentry>
 954           <varlistentry>
 955             <term>flags</term>
 956             <listitem>
 957               <para>The list of what to allow, all the oper lines above this
 958               (up to another flags entry) will receive these flags.
 959               They are listed below.</para>
 960             </listitem>
 961           </varlistentry>
 962         </variablelist>
 963         <note><para>
 964           While they have the same names, the flags have subtly different
 965           meanings from those in the cluster{} block.
 966         </para></note>
 967         <variablelist>
 968           <title>shared {} flags</title>
 969           <varlistentry>
 970             <term>kline (K)</term>
 971             <listitem>
 972               <para>Permanent and temporary K:lines</para>
 973             </listitem>
 974           </varlistentry>
 975           <varlistentry>
 976             <term>tkline (k)</term>
 977             <listitem>
 978               <para>Temporary K:lines</para>
 979             </listitem>
 980           </varlistentry>
 981           <varlistentry>
 982             <term>unkline (U)</term>
 983             <listitem>
 984               <para>K:line removals</para>
 985             </listitem>
 986           </varlistentry>
 987           <varlistentry>
 988             <term>xline (X)</term>
 989             <listitem>
 990               <para>Permanent and temporary X:lines</para>
 991             </listitem>
 992           </varlistentry>
 993           <varlistentry>
 994             <term>txline (x)</term>
 995             <listitem>
 996               <para>Temporary X:lines</para>
 997             </listitem>
 998           </varlistentry>
 999           <varlistentry>
1000             <term>unxline (Y)</term>
1001             <listitem>
1002               <para>X:line removals</para>
1003             </listitem>
1004           </varlistentry>
1005           <varlistentry>
1006             <term>resv (Q)</term>
1007             <listitem>
1008               <para>Permanently and temporarily reserved nicks/channels</para>
1009             </listitem>
1010           </varlistentry>
1011           <varlistentry>
1012             <term>tresv (q)</term>
1013             <listitem>
1014               <para>Temporarily reserved nicks/channels</para>
1015             </listitem>
1016           </varlistentry>
1017           <varlistentry>
1018             <term>unresv (R)</term>
1019             <listitem>
1020               <para>RESV removals</para>
1021             </listitem>
1022           </varlistentry>
1023           <varlistentry>
1024             <term>all</term>
1025             <listitem>
1026               <para>All of the above; this does not include locops or rehash</para>
1027             </listitem>
1028           </varlistentry>
1029           <varlistentry>
1030             <term>locops (L)</term>
1031             <listitem>
1032               <para>LOCOPS messages (accepting this from * makes LOCOPS rather
1033               similar to OPERWALL which is not useful); unlike the other flags,
1034               this can only be accepted from *@* although it can be
1035               restricted based on source server.</para>
1036             </listitem>
1037           </varlistentry>
1038           <varlistentry>
1039             <term>rehash (H)</term>
1040             <listitem>
1041               <para>REHASH commands; all options can be used</para>
1042             </listitem>
1043           </varlistentry>
1044           <varlistentry>
1045             <term>none</term>
1046             <listitem>
1047               <para>Allow nothing to be done</para>
1048             </listitem>
1049           </varlistentry>
1050         </variablelist>
1051       </sect2>
1052       <sect2>
1053         <title>service {} block</title>
1054         <synopsis>
1055 service {
1056         name = "<replaceable>text</replaceable>";
1057 };</synopsis>
1058         <para>
1059           The service block specifies privileged servers (services). These
1060           servers have extra privileges such as setting login names on users
1061           and introducing clients with umode +S (unkickable, hide channels, etc).
1062           This does not allow them to set bans, you need a separate shared{}
1063           block for that.
1064         </para>
1065         <para>
1066           Do not place normal servers here.
1067         </para>
1068         <para>
1069           Multiple names may be specified but there may be only one service{}
1070           block.
1071         </para>
1072         <variablelist>
1073           <title>service {} variables</title>
1074           <varlistentry>
1075             <term>name</term>
1076             <listitem>
1077               <para>The server name to grant special privileges. This may not
1078               contain wildcards.</para>
1079             </listitem>
1080           </varlistentry>
1081         </variablelist>
1082       </sect2>
1083     </sect1>
1084   </chapter>
1085 <!-- Keep this comment at the end of the file
1086 Local variables:
1087 mode: sgml
1088 sgml-omittag:t
1089 sgml-shorttag:t
1090 sgml-namecase-general:t
1091 sgml-general-insert-case:lower
1092 sgml-minimize-attributes:nil
1093 sgml-always-quote-attributes:t
1094 sgml-indent-step:2
1095 sgml-indent-data:t
1096 sgml-parent-document: ("dancer-oper-guide.sgml" "book")
1097 sgml-exposed-tags:nil
1098 fill-column:105
1099 sgml-validate-command: "nsgmls -e -g -s -u dancer-oper-guide.sgml"
1100 End:
1101 -->