Les De Ridder
||3 years ago|
|source/ircd||3 years ago|
|.gitignore||3 years ago|
|LICENSE||4 years ago|
|README.md||3 years ago|
|config.template.sdl||4 years ago|
|dub.sdl||3 years ago|
|dub.selections.json||3 years ago|
|generate-version-info.fish||3 years ago|
The main goals of salty-ircd are strict RFC compliance and security.
salty-ircd aims to be fully compliant with the IRC RFCs (by default), specifically RFC 1459, RFC 2811, RFC 2812, and RFC 2813 (planned), including all errata. Newer RFCs take precedence over older RFCs.
Any additional features breaking RFC compliance are available through compile-time options.
The following rules apply when any compile-time option is enabled (breaking strict RFC compliance):
- TLS is required for all connections, except connections from localhost (useful for running a Tor hidden service, which already has encryption)
- TLS client certificates are required for oper and vhost authentication
- A D compiler
- RFC compliant:
- Modern (all additional features):
dub build -c=modern
The 'modern' configuration aims to be mostly compatible with UnrealIRCd user modes/chars.
-d=ProxyV1 is added to the build command, salty-ircd can accept traffic through the PROXY protocol (version 1), e.g. from an UnrealIRCd server running with a custom module. Please see this module's readme for more information. Note that this is simply a development/debugging option and should not be used for a production server.
TODO: Add a method to supply a custom list of compile-time options.
First, create the configuration file,
config.sdl. You can find a template in
Then, simply run