2016-04-13 00:55:37 +02:00
|
|
|
# oragono IRCd config
|
2016-04-12 07:44:00 +02:00
|
|
|
|
|
|
|
# network configuration
|
|
|
|
network:
|
|
|
|
# name of the network
|
|
|
|
name: OragonoTest
|
|
|
|
|
|
|
|
# server configuration
|
2016-04-12 15:00:09 +02:00
|
|
|
server:
|
|
|
|
# server name
|
2016-04-13 00:55:37 +02:00
|
|
|
name: oragono.test
|
2016-04-12 15:00:09 +02:00
|
|
|
|
|
|
|
# addresses to listen on
|
|
|
|
listen:
|
|
|
|
- ":6667"
|
2016-04-13 12:45:09 +02:00
|
|
|
- ":6697" # ssl port
|
2019-01-31 09:43:48 +01:00
|
|
|
# Binding on specific IPs:
|
|
|
|
# - "127.0.0.1:6668"
|
|
|
|
# - "[::1]:6668"
|
2018-08-28 19:34:43 +02:00
|
|
|
# Unix domain socket for proxying:
|
2018-02-01 21:53:49 +01:00
|
|
|
# - "/tmp/oragono_sock"
|
2016-04-12 15:00:09 +02:00
|
|
|
|
2018-08-29 03:10:54 +02:00
|
|
|
# sets the permissions for Unix listen sockets. on a typical Linux system,
|
|
|
|
# the default is 0775 or 0755, which prevents other users/groups from connecting
|
|
|
|
# to the socket. With 0777, it behaves like a normal TCP socket
|
|
|
|
# where anyone can connect.
|
|
|
|
unix-bind-mode: 0777
|
2018-08-28 19:34:43 +02:00
|
|
|
|
2016-04-28 12:12:23 +02:00
|
|
|
# tls listeners
|
|
|
|
tls-listeners:
|
|
|
|
# listener on ":6697"
|
|
|
|
":6697":
|
|
|
|
key: tls.key
|
|
|
|
cert: tls.crt
|
2017-04-30 04:35:07 +02:00
|
|
|
|
2017-03-09 10:07:35 +01:00
|
|
|
# strict transport security, to get clients to automagically use TLS
|
|
|
|
sts:
|
|
|
|
# whether to advertise STS
|
|
|
|
#
|
|
|
|
# to stop advertising STS, leave this enabled and set 'duration' below to "0". this will
|
|
|
|
# advertise to connecting users that the STS policy they have saved is no longer valid
|
2017-03-09 10:12:53 +01:00
|
|
|
enabled: false
|
2017-03-09 10:07:35 +01:00
|
|
|
|
|
|
|
# how long clients should be forced to use TLS for.
|
2017-03-09 10:15:32 +01:00
|
|
|
# setting this to a too-long time will mean bad things if you later remove your TLS.
|
|
|
|
# the default duration below is 1 month, 2 days and 5 minutes.
|
|
|
|
duration: 1mo2d5m
|
2017-03-09 10:07:35 +01:00
|
|
|
|
|
|
|
# tls port - you should be listening on this port above
|
|
|
|
port: 6697
|
|
|
|
|
|
|
|
# should clients include this STS policy when they ship their inbuilt preload lists?
|
|
|
|
preload: false
|
2016-04-12 15:00:09 +02:00
|
|
|
|
2016-06-30 11:28:34 +02:00
|
|
|
# use ident protocol to get usernames
|
|
|
|
check-ident: true
|
|
|
|
|
2016-04-12 15:00:09 +02:00
|
|
|
# password to login to the server
|
2016-04-13 00:55:37 +02:00
|
|
|
# generated using "oragono genpasswd"
|
2016-04-12 15:00:09 +02:00
|
|
|
#password: ""
|
|
|
|
|
|
|
|
# motd filename
|
2016-04-12 08:34:47 +02:00
|
|
|
# if you change the motd, you should move it to ircd.motd
|
|
|
|
motd: oragono.motd
|
2016-04-12 15:00:09 +02:00
|
|
|
|
2017-10-08 12:17:49 +02:00
|
|
|
# motd formatting codes
|
|
|
|
# if this is true, the motd is escaped using formatting codes like $c, $b, and $i
|
2018-04-11 01:26:42 +02:00
|
|
|
motd-formatting: true
|
2017-10-08 12:17:49 +02:00
|
|
|
|
2017-09-11 07:04:08 +02:00
|
|
|
# addresses/hostnames the PROXY command can be used from
|
2018-02-01 21:53:49 +01:00
|
|
|
# this should be restricted to 127.0.0.1/8 and localhost at most
|
2017-09-11 08:50:41 +02:00
|
|
|
# you should also add these addresses to the connection limits and throttling exemption lists
|
|
|
|
proxy-allowed-from:
|
|
|
|
# - localhost
|
|
|
|
# - "127.0.0.1"
|
2018-02-01 21:53:49 +01:00
|
|
|
# - "127.0.0.1/8"
|
2017-09-11 07:04:08 +02:00
|
|
|
|
2017-10-15 08:18:14 +02:00
|
|
|
# controls the use of the WEBIRC command (by IRC<->web interfaces, bouncers and similar)
|
|
|
|
webirc:
|
|
|
|
# one webirc block -- should correspond to one set of gateways
|
|
|
|
-
|
2017-10-16 00:47:49 +02:00
|
|
|
# tls fingerprint the gateway must connect with to use this webirc block
|
|
|
|
fingerprint: 938dd33f4b76dcaf7ce5eb25c852369cb4b8fb47ba22fc235aa29c6623a5f182
|
|
|
|
|
2017-10-15 08:18:14 +02:00
|
|
|
# password the gateway uses to connect, made with oragono genpasswd
|
2018-08-06 04:51:39 +02:00
|
|
|
password: "$2a$04$sLEFDpIOyUp55e6gTMKbOeroT6tMXTjPFvA0eGvwvImVR9pkwv7ee"
|
2017-10-15 08:18:14 +02:00
|
|
|
|
|
|
|
# hosts that can use this webirc command
|
2018-02-25 11:18:54 +01:00
|
|
|
# you should also add these addresses to the connection limits and throttling exemption lists
|
2017-10-15 08:18:14 +02:00
|
|
|
hosts:
|
|
|
|
# - localhost
|
|
|
|
# - "127.0.0.1"
|
2018-02-01 21:53:49 +01:00
|
|
|
# - "127.0.0.1/8"
|
2017-10-15 08:18:14 +02:00
|
|
|
# - "0::1"
|
|
|
|
|
2018-11-26 11:23:27 +01:00
|
|
|
# allow use of the RESUME extension over plaintext connections:
|
|
|
|
# do not enable this unless the ircd is only accessible over internal networks
|
|
|
|
allow-plaintext-resume: false
|
|
|
|
|
2017-03-13 23:12:39 +01:00
|
|
|
# maximum length of clients' sendQ in bytes
|
2017-03-23 03:12:39 +01:00
|
|
|
# this should be big enough to hold /LIST and HELP replies
|
2017-03-13 23:12:39 +01:00
|
|
|
max-sendq: 16k
|
|
|
|
|
2016-10-23 15:05:00 +02:00
|
|
|
# maximum number of connections per subnet
|
|
|
|
connection-limits:
|
2017-10-09 19:48:58 +02:00
|
|
|
# whether to enforce connection limits or not
|
2017-01-12 08:40:01 +01:00
|
|
|
enabled: true
|
|
|
|
|
2017-04-30 04:35:07 +02:00
|
|
|
# how wide the cidr should be for IPv4
|
2017-10-02 05:59:02 +02:00
|
|
|
cidr-len-ipv4: 32
|
2016-10-23 15:05:00 +02:00
|
|
|
|
|
|
|
# how wide the cidr should be for IPv6
|
2017-10-02 05:59:02 +02:00
|
|
|
cidr-len-ipv6: 64
|
2016-10-23 15:05:00 +02:00
|
|
|
|
2018-02-25 11:17:39 +01:00
|
|
|
# maximum concurrent connections per subnet (defined above by the cidr length)
|
|
|
|
connections-per-subnet: 16
|
2016-10-23 15:05:00 +02:00
|
|
|
|
|
|
|
# IPs/networks which are exempted from connection limits
|
|
|
|
exempted:
|
|
|
|
- "127.0.0.1"
|
|
|
|
- "127.0.0.1/8"
|
|
|
|
- "::1/128"
|
|
|
|
|
2017-01-12 08:40:01 +01:00
|
|
|
# automated connection throttling
|
|
|
|
connection-throttling:
|
|
|
|
# whether to throttle connections or not
|
|
|
|
enabled: true
|
|
|
|
|
2017-04-30 04:35:07 +02:00
|
|
|
# how wide the cidr should be for IPv4
|
2017-01-12 08:40:01 +01:00
|
|
|
cidr-len-ipv4: 32
|
|
|
|
|
|
|
|
# how wide the cidr should be for IPv6
|
2017-10-10 23:48:31 +02:00
|
|
|
cidr-len-ipv6: 64
|
2017-01-12 08:40:01 +01:00
|
|
|
|
|
|
|
# how long to keep track of connections for
|
|
|
|
duration: 10m
|
|
|
|
|
|
|
|
# maximum number of connections, per subnet, within the given duration
|
2017-10-10 23:48:31 +02:00
|
|
|
max-connections: 32
|
2017-01-12 08:40:01 +01:00
|
|
|
|
|
|
|
# how long to ban offenders for, and the message to use
|
|
|
|
# after banning them, the number of connections is reset (which lets you use UNDLINE to unban people)
|
|
|
|
ban-duration: 10m
|
|
|
|
ban-message: You have attempted to connect too many times within a short duration. Wait a while, and you will be able to connect.
|
|
|
|
|
|
|
|
# IPs/networks which are exempted from connection limits
|
|
|
|
exempted:
|
|
|
|
- "127.0.0.1"
|
|
|
|
- "127.0.0.1/8"
|
|
|
|
- "::1/128"
|
|
|
|
|
2017-03-06 00:43:52 +01:00
|
|
|
# account options
|
|
|
|
accounts:
|
2016-09-05 15:01:40 +02:00
|
|
|
# account registration
|
2017-03-06 00:43:52 +01:00
|
|
|
registration:
|
2016-09-05 15:01:40 +02:00
|
|
|
# can users register new accounts?
|
|
|
|
enabled: true
|
|
|
|
|
2018-08-06 04:51:39 +02:00
|
|
|
# this is the bcrypt cost we'll use for account passwords
|
|
|
|
bcrypt-cost: 12
|
|
|
|
|
2016-09-05 15:01:40 +02:00
|
|
|
# length of time a user has to verify their account before it can be re-registered
|
2018-02-28 23:31:56 +01:00
|
|
|
verify-timeout: "32h"
|
2016-09-05 15:01:40 +02:00
|
|
|
|
|
|
|
# callbacks to allow
|
|
|
|
enabled-callbacks:
|
|
|
|
- none # no verification needed, will instantly register successfully
|
2018-02-20 10:20:30 +01:00
|
|
|
|
|
|
|
# example configuration for sending verification emails via a local mail relay
|
|
|
|
# callbacks:
|
|
|
|
# mailto:
|
|
|
|
# server: localhost
|
|
|
|
# port: 25
|
|
|
|
# tls:
|
|
|
|
# enabled: false
|
|
|
|
# username: ""
|
|
|
|
# password: ""
|
|
|
|
# sender: "admin@my.network"
|
|
|
|
|
2017-03-06 00:43:52 +01:00
|
|
|
# is account authentication enabled?
|
|
|
|
authentication-enabled: true
|
2016-10-23 15:14:13 +02:00
|
|
|
|
2019-01-01 22:45:37 +01:00
|
|
|
# throttle account login attempts (to prevent either password guessing, or DoS
|
|
|
|
# attacks on the server aimed at forcing repeated expensive bcrypt computations)
|
|
|
|
login-throttling:
|
|
|
|
enabled: true
|
|
|
|
|
|
|
|
# window
|
|
|
|
duration: 1m
|
|
|
|
|
|
|
|
# number of attempts allowed within the window
|
|
|
|
max-attempts: 3
|
|
|
|
|
2018-02-27 03:44:03 +01:00
|
|
|
# some clients (notably Pidgin and Hexchat) offer only a single password field,
|
|
|
|
# which makes it impossible to specify a separate server password (for the PASS
|
|
|
|
# command) and SASL password. if this option is set to true, a client that
|
|
|
|
# successfully authenticates with SASL will not be required to send
|
|
|
|
# PASS as well, so it can be configured to authenticate with SASL only.
|
|
|
|
skip-server-password: false
|
|
|
|
|
2018-02-18 10:46:14 +01:00
|
|
|
# nick-reservation controls how, and whether, nicknames are linked to accounts
|
|
|
|
nick-reservation:
|
|
|
|
# is there any enforcement of reserved nicknames?
|
|
|
|
enabled: false
|
|
|
|
|
2018-03-02 23:04:24 +01:00
|
|
|
# how many nicknames, in addition to the account name, can be reserved?
|
|
|
|
additional-nick-limit: 2
|
|
|
|
|
2018-02-18 10:46:14 +01:00
|
|
|
# method describes how nickname reservation is handled
|
2019-01-02 16:08:44 +01:00
|
|
|
# already logged-in using SASL or NickServ
|
|
|
|
# timeout: let the user change to the registered nickname, give them X seconds
|
|
|
|
# to login and then rename them if they haven't done so
|
|
|
|
# strict: don't let the user change to the registered nickname unless they're
|
|
|
|
# already logged-in using SASL or NickServ
|
|
|
|
# optional: no enforcement by default, but allow users to opt in to
|
|
|
|
# the enforcement level of their choice
|
2018-02-18 10:46:14 +01:00
|
|
|
method: timeout
|
|
|
|
|
2019-01-02 16:08:44 +01:00
|
|
|
# allow users to set their own nickname enforcement status, e.g.,
|
|
|
|
# to opt in to strict enforcement
|
|
|
|
allow-custom-enforcement: true
|
|
|
|
|
2018-02-18 10:46:14 +01:00
|
|
|
# rename-timeout - this is how long users have 'til they're renamed
|
|
|
|
rename-timeout: 30s
|
|
|
|
|
|
|
|
# rename-prefix - this is the prefix to use when renaming clients (e.g. Guest-AB54U31)
|
|
|
|
rename-prefix: Guest-
|
2018-02-11 11:30:40 +01:00
|
|
|
|
2018-04-23 08:38:35 +02:00
|
|
|
# vhosts controls the assignment of vhosts (strings displayed in place of the user's
|
|
|
|
# hostname/IP) by the HostServ service
|
|
|
|
vhosts:
|
|
|
|
# are vhosts enabled at all?
|
2018-04-19 08:48:19 +02:00
|
|
|
enabled: true
|
2018-04-23 08:38:35 +02:00
|
|
|
|
2018-04-19 08:48:19 +02:00
|
|
|
# maximum length of a vhost
|
2018-04-23 08:38:35 +02:00
|
|
|
max-length: 64
|
|
|
|
|
2018-04-19 08:48:19 +02:00
|
|
|
# regexp for testing the validity of a vhost
|
|
|
|
# (make sure any changes you make here are RFC-compliant)
|
|
|
|
valid-regexp: '^[0-9A-Za-z.\-_/]+$'
|
|
|
|
|
2018-04-23 08:38:35 +02:00
|
|
|
# options controlling users requesting vhosts:
|
|
|
|
user-requests:
|
|
|
|
# can users request vhosts at all? if this is false, operators with the
|
|
|
|
# 'vhosts' capability can still assign vhosts manually
|
|
|
|
enabled: false
|
|
|
|
|
|
|
|
# if uncommented, all new vhost requests will be dumped into the given
|
|
|
|
# channel, so opers can review them as they are sent in. ensure that you
|
|
|
|
# have registered and restricted the channel appropriately before you
|
|
|
|
# uncomment this.
|
|
|
|
#channel: "#vhosts"
|
|
|
|
|
|
|
|
# after a user's vhost has been approved or rejected, they need to wait
|
|
|
|
# this long (starting from the time of their original request)
|
|
|
|
# before they can request a new one.
|
|
|
|
cooldown: 168h
|
|
|
|
|
2017-03-24 03:52:38 +01:00
|
|
|
# channel options
|
|
|
|
channels:
|
2017-09-06 23:34:38 +02:00
|
|
|
# modes that are set when new channels are created
|
|
|
|
# +n is no-external-messages and +t is op-only-topic
|
|
|
|
# see /QUOTE HELP cmodes for more channel modes
|
|
|
|
default-modes: +nt
|
|
|
|
|
2017-03-24 03:52:38 +01:00
|
|
|
# channel registration - requires an account
|
|
|
|
registration:
|
|
|
|
# can users register new channels?
|
|
|
|
enabled: true
|
|
|
|
|
2016-10-23 02:47:11 +02:00
|
|
|
# operator classes
|
|
|
|
oper-classes:
|
|
|
|
# local operator
|
|
|
|
"local-oper":
|
|
|
|
# title shown in WHOIS
|
|
|
|
title: Local Operator
|
|
|
|
|
|
|
|
# capability names
|
|
|
|
capabilities:
|
|
|
|
- "oper:local_kill"
|
|
|
|
- "oper:local_ban"
|
|
|
|
- "oper:local_unban"
|
2018-03-22 16:04:21 +01:00
|
|
|
- "nofakelag"
|
2016-10-23 02:47:11 +02:00
|
|
|
|
|
|
|
# network operator
|
|
|
|
"network-oper":
|
|
|
|
# title shown in WHOIS
|
|
|
|
title: Network Operator
|
|
|
|
|
|
|
|
# oper class this extends from
|
|
|
|
extends: "local-oper"
|
|
|
|
|
|
|
|
# capability names
|
|
|
|
capabilities:
|
|
|
|
- "oper:remote_kill"
|
|
|
|
- "oper:remote_ban"
|
|
|
|
- "oper:remote_unban"
|
|
|
|
|
|
|
|
# server admin
|
|
|
|
"server-admin":
|
|
|
|
# title shown in WHOIS
|
|
|
|
title: Server Admin
|
|
|
|
|
|
|
|
# oper class this extends from
|
|
|
|
extends: "local-oper"
|
|
|
|
|
|
|
|
# capability names
|
|
|
|
capabilities:
|
|
|
|
- "oper:rehash"
|
|
|
|
- "oper:die"
|
2018-06-19 10:03:40 +02:00
|
|
|
- "accreg"
|
2018-05-25 08:46:36 +02:00
|
|
|
- "sajoin"
|
2017-01-23 00:36:13 +01:00
|
|
|
- "samode"
|
2018-04-23 08:38:35 +02:00
|
|
|
- "vhosts"
|
2018-05-25 06:38:20 +02:00
|
|
|
- "chanreg"
|
2016-10-23 02:47:11 +02:00
|
|
|
|
2016-04-12 15:00:09 +02:00
|
|
|
# ircd operators
|
2016-10-23 02:47:11 +02:00
|
|
|
opers:
|
2016-04-12 15:00:09 +02:00
|
|
|
# operator named 'dan'
|
|
|
|
dan:
|
2016-10-23 02:47:11 +02:00
|
|
|
# which capabilities this oper has access to
|
|
|
|
class: "server-admin"
|
|
|
|
|
2016-10-23 03:01:05 +02:00
|
|
|
# custom whois line
|
|
|
|
whois-line: is a cool dude
|
|
|
|
|
2016-10-23 02:47:11 +02:00
|
|
|
# custom hostname
|
|
|
|
vhost: "n"
|
|
|
|
|
2017-05-08 01:15:16 +02:00
|
|
|
# modes are the modes to auto-set upon opering-up
|
|
|
|
modes: +is acjknoqtux
|
|
|
|
|
2016-04-12 15:00:09 +02:00
|
|
|
# password to login with /OPER command
|
2016-04-13 00:55:37 +02:00
|
|
|
# generated using "oragono genpasswd"
|
2018-08-06 04:51:39 +02:00
|
|
|
password: "$2a$04$LiytCxaY0lI.guDj2pBN4eLRD5cdM2OLDwqmGAgB6M2OPirbF5Jcu"
|
2016-08-12 14:20:32 +02:00
|
|
|
|
2017-03-06 04:08:46 +01:00
|
|
|
# logging, takes inspiration from Insp
|
|
|
|
logging:
|
|
|
|
-
|
|
|
|
# how to log these messages
|
|
|
|
#
|
|
|
|
# file log to given target filename
|
2017-05-01 10:51:37 +02:00
|
|
|
# stdout log to stdout
|
2017-03-06 04:08:46 +01:00
|
|
|
# stderr log to stderr
|
|
|
|
method: file stderr
|
|
|
|
|
|
|
|
# filename to log to, if file method is selected
|
|
|
|
filename: ircd.log
|
|
|
|
|
|
|
|
# type(s) of logs to keep here. you can use - to exclude those types
|
|
|
|
#
|
|
|
|
# exclusions take precedent over inclusions, so if you exclude a type it will NEVER
|
|
|
|
# be logged, even if you explicitly include it
|
|
|
|
#
|
|
|
|
# useful types include:
|
|
|
|
# * everything (usually used with exclusing some types below)
|
2019-02-03 03:12:17 +01:00
|
|
|
# server server startup, rehash, and shutdown events
|
2017-03-06 04:08:46 +01:00
|
|
|
# accounts account registration and authentication
|
|
|
|
# channels channel creation and operations
|
|
|
|
# commands command calling and operations
|
|
|
|
# opers oper actions, authentication, etc
|
|
|
|
# password password hashing and comparing
|
|
|
|
# userinput raw lines sent by users
|
|
|
|
# useroutput raw lines sent to users
|
2017-03-06 13:11:10 +01:00
|
|
|
type: "* -userinput -useroutput -localconnect -localconnect-ip"
|
2017-03-06 04:08:46 +01:00
|
|
|
|
|
|
|
# one of: debug info warn error
|
2017-03-06 13:11:10 +01:00
|
|
|
level: info
|
|
|
|
-
|
|
|
|
# avoid logging IP addresses to file
|
|
|
|
method: stderr
|
|
|
|
type: localconnect localconnect-ip
|
|
|
|
level: debug
|
2017-03-06 04:08:46 +01:00
|
|
|
|
2017-04-30 04:35:07 +02:00
|
|
|
# debug options
|
|
|
|
debug:
|
2017-10-26 10:19:01 +02:00
|
|
|
# when enabled, oragono will attempt to recover from certain kinds of
|
|
|
|
# client-triggered runtime errors that would normally crash the server.
|
|
|
|
# this makes the server more resilient to DoS, but could result in incorrect
|
|
|
|
# behavior. deployments that would prefer to "start from scratch", e.g., by
|
|
|
|
# letting the process crash and auto-restarting it with systemd, can set
|
|
|
|
# this to false.
|
|
|
|
recover-from-errors: true
|
|
|
|
|
2018-03-13 19:46:39 +01:00
|
|
|
# optionally expose a pprof http endpoint: https://golang.org/pkg/net/http/pprof/
|
|
|
|
# it is strongly recommended that you don't expose this on a public interface;
|
|
|
|
# if you need to access it remotely, you can use an SSH tunnel.
|
|
|
|
# set to `null`, "", leave blank, or omit to disable
|
2018-03-13 23:04:15 +01:00
|
|
|
# pprof-listener: "localhost:6060"
|
2018-03-13 19:46:39 +01:00
|
|
|
|
2016-09-04 11:25:33 +02:00
|
|
|
# datastore configuration
|
|
|
|
datastore:
|
|
|
|
# path to the datastore
|
|
|
|
path: ircd.db
|
|
|
|
|
2018-04-20 09:57:48 +02:00
|
|
|
# if the database schema requires an upgrade, `autoupgrade` will attempt to
|
|
|
|
# perform it automatically on startup. the database will be backed
|
2018-04-16 22:28:31 +02:00
|
|
|
# up, and if the upgrade fails, the original database will be restored.
|
|
|
|
autoupgrade: true
|
2016-09-04 11:25:33 +02:00
|
|
|
|
2018-01-22 08:30:31 +01:00
|
|
|
# languages config
|
|
|
|
languages:
|
|
|
|
# whether to load languages
|
2018-04-11 01:26:42 +02:00
|
|
|
enabled: true
|
2018-01-22 08:30:31 +01:00
|
|
|
|
|
|
|
# default language to use for new clients
|
|
|
|
# 'en' is the default English language in the code
|
|
|
|
default: en
|
|
|
|
|
|
|
|
# which directory contains our language files
|
|
|
|
path: languages
|
|
|
|
|
2016-08-12 14:20:32 +02:00
|
|
|
# limits - these need to be the same across the network
|
|
|
|
limits:
|
|
|
|
# nicklen is the max nick length allowed
|
|
|
|
nicklen: 32
|
|
|
|
|
2019-02-03 10:24:59 +01:00
|
|
|
# identlen is the max ident length allowed
|
2019-02-03 20:01:46 +01:00
|
|
|
identlen: 20
|
2019-02-03 10:24:59 +01:00
|
|
|
|
2016-08-12 14:20:32 +02:00
|
|
|
# channellen is the max channel length allowed
|
|
|
|
channellen: 64
|
2016-08-14 06:07:50 +02:00
|
|
|
|
2016-09-12 04:40:09 +02:00
|
|
|
# awaylen is the maximum length of an away message
|
2016-11-29 09:38:04 +01:00
|
|
|
awaylen: 500
|
2016-09-12 04:40:09 +02:00
|
|
|
|
2016-09-12 04:22:50 +02:00
|
|
|
# kicklen is the maximum length of a kick message
|
2016-11-29 09:38:04 +01:00
|
|
|
kicklen: 1000
|
2016-09-12 04:22:50 +02:00
|
|
|
|
|
|
|
# topiclen is the maximum length of a channel topic
|
2016-11-29 09:38:04 +01:00
|
|
|
topiclen: 1000
|
2016-09-12 04:22:50 +02:00
|
|
|
|
2016-10-16 12:14:56 +02:00
|
|
|
# maximum number of monitor entries a client can have
|
|
|
|
monitor-entries: 100
|
|
|
|
|
2016-08-14 06:07:50 +02:00
|
|
|
# whowas entries to store
|
|
|
|
whowas-entries: 100
|
2016-10-23 16:50:18 +02:00
|
|
|
|
|
|
|
# maximum length of channel lists (beI modes)
|
|
|
|
chan-list-modes: 60
|
2016-11-29 09:38:04 +01:00
|
|
|
|
|
|
|
# maximum length of IRC lines
|
2017-01-18 00:46:30 +01:00
|
|
|
# this should generally be 1024-2048, and will only apply when negotiated by clients
|
2017-01-13 15:22:42 +01:00
|
|
|
linelen:
|
|
|
|
# tags section
|
|
|
|
tags: 2048
|
|
|
|
|
|
|
|
# rest of the message
|
|
|
|
rest: 2048
|
2018-03-22 16:04:21 +01:00
|
|
|
|
|
|
|
# fakelag: prevents clients from spamming commands too rapidly
|
|
|
|
fakelag:
|
|
|
|
# whether to enforce fakelag
|
2018-03-28 19:18:08 +02:00
|
|
|
enabled: false
|
2018-03-22 16:04:21 +01:00
|
|
|
|
|
|
|
# time unit for counting command rates
|
|
|
|
window: 1s
|
|
|
|
|
|
|
|
# clients can send this many commands without fakelag being imposed
|
|
|
|
burst-limit: 5
|
|
|
|
|
|
|
|
# once clients have exceeded their burst allowance, they can send only
|
|
|
|
# this many commands per `window`:
|
|
|
|
messages-per-window: 2
|
2018-03-28 19:18:08 +02:00
|
|
|
|
|
|
|
# client status resets to the default state if they go this long without
|
|
|
|
# sending any commands:
|
2018-04-01 01:43:55 +02:00
|
|
|
cooldown: 2s
|
2018-11-26 11:23:27 +01:00
|
|
|
|
|
|
|
# message history tracking, for the RESUME extension and possibly other uses in future
|
|
|
|
history:
|
|
|
|
# should we store messages for later playback?
|
2019-02-05 10:29:32 +01:00
|
|
|
# the current implementation stores messages in RAM only; they do not persist
|
|
|
|
# across server restarts. however, you should disable this unless you understand
|
|
|
|
# how it interacts with the GDPR and/or any data privacy laws that apply
|
|
|
|
# in your country and the countries of your users.
|
2018-11-26 11:23:27 +01:00
|
|
|
enabled: true
|
|
|
|
|
|
|
|
# how many channel-specific events (messages, joins, parts) should be tracked per channel?
|
|
|
|
channel-length: 256
|
|
|
|
|
|
|
|
# how many direct messages and notices should be tracked per user?
|
|
|
|
client-length: 64
|
2018-12-28 19:45:55 +01:00
|
|
|
|
|
|
|
# number of messages to automatically play back on channel join (0 to disable):
|
|
|
|
autoreplay-on-join: 0
|
2019-02-04 18:16:28 +01:00
|
|
|
|
|
|
|
# maximum number of CHATHISTORY messages that can be
|
|
|
|
# requested at once (0 disables support for CHATHISTORY)
|
|
|
|
chathistory-maxmessages: 100
|