ergo/oragono.yaml

387 lines
12 KiB
YAML
Raw Normal View History

# oragono IRCd config
2016-04-12 07:44:00 +02:00
# network configuration
network:
# name of the network
name: OragonoTest
# server configuration
server:
# server name
name: oragono.test
# addresses to listen on
listen:
- ":6667"
- "127.0.0.1:6668"
- "[::1]:6668"
- ":6697" # ssl port
2018-02-01 21:53:49 +01:00
# unix domain socket for proxying:
# - "/tmp/oragono_sock"
# tls listeners
tls-listeners:
# listener on ":6697"
":6697":
key: tls.key
cert: tls.crt
2017-04-30 04:35:07 +02: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
# how long clients should be forced to use TLS for.
# 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
# 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
# use ident protocol to get usernames
check-ident: true
# password to login to the server
# generated using "oragono genpasswd"
#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
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
#motd-formatting: true
# 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
# 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-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
-
# 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
password: JDJhJDA0JG9rTTVERlNRa0hpOEZpNkhjZE95SU9Da1BseFdlcWtOTEQxNEFERVlqbEZNTkdhOVlYUkMu
# hosts that can use this webirc command
# 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"
2017-03-13 23:12:39 +01:00
# maximum length of clients' sendQ in bytes
# this should be big enough to hold /LIST and HELP replies
2017-03-13 23:12:39 +01:00
max-sendq: 16k
# maximum number of connections per subnet
connection-limits:
2017-10-09 19:48:58 +02:00
# whether to enforce connection limits or not
enabled: true
2017-04-30 04:35:07 +02:00
# how wide the cidr should be for IPv4
cidr-len-ipv4: 32
# how wide the cidr should be for IPv6
cidr-len-ipv6: 64
2018-02-25 11:17:39 +01:00
# maximum concurrent connections per subnet (defined above by the cidr length)
connections-per-subnet: 16
# IPs/networks which are exempted from connection limits
exempted:
- "127.0.0.1"
- "127.0.0.1/8"
- "::1/128"
# 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
cidr-len-ipv4: 32
# how wide the cidr should be for IPv6
cidr-len-ipv6: 64
# how long to keep track of connections for
duration: 10m
# maximum number of connections, per subnet, within the given duration
max-connections: 32
# 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"
# account options
accounts:
# account registration
registration:
# can users register new accounts?
enabled: true
# 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"
# 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"
# allow multiple account registrations per connection
# this is for testing purposes and shouldn't be allowed on real networks
allow-multiple-per-connection: false
# is account authentication enabled?
authentication-enabled: true
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
# nick-reservation controls how, and whether, nicknames are linked to accounts
nick-reservation:
# is there any enforcement of reserved nicknames?
enabled: false
# method describes how nickname reservation is handled
# 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
method: timeout
# 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-
# channel options
channels:
# 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
# channel registration - requires an account
registration:
# can users register new channels?
enabled: true
# 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"
# 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"
- "unregister"
- "samode"
# ircd operators
opers:
# operator named 'dan'
dan:
# which capabilities this oper has access to
class: "server-admin"
# custom whois line
whois-line: is a cool dude
# 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
# password to login with /OPER command
# generated using "oragono genpasswd"
password: JDJhJDA0JE1vZmwxZC9YTXBhZ3RWT2xBbkNwZnV3R2N6VFUwQUI0RUJRVXRBRHliZVVoa0VYMnlIaGsu
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)
# 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
type: "* -userinput -useroutput -localconnect -localconnect-ip"
2017-03-06 04:08:46 +01:00
# one of: debug info warn error
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
# 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
pprof-listener: "localhost:6060"
2017-04-30 04:35:07 +02:00
# enabling StackImpact profiling
stackimpact:
# whether to use StackImpact
enabled: false
# the AgentKey to use
agent-key: examplekeyhere
# the app name to report
app-name: Oragono
# datastore configuration
datastore:
# path to the datastore
path: ircd.db
2018-01-22 08:30:31 +01:00
# languages config
languages:
# whether to load languages
enabled: false
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
# limits - these need to be the same across the network
limits:
# nicklen is the max nick length allowed
nicklen: 32
# channellen is the max channel length allowed
channellen: 64
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
# 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
linelen:
# tags section
tags: 2048
# rest of the message
rest: 2048