A modern IRC server (daemon/ircd) written in Go.

Overview

Oragono logo

Oragono is a modern IRC server written in Go. Its core design principles are:

  • Being simple to set up and use
  • Combining the features of an ircd, a services framework, and a bouncer (integrated account management, history storage, and bouncer functionality)
  • Bleeding-edge IRCv3 support, suitable for use as an IRCv3 reference implementation
  • Highly customizable via a rehashable (i.e., reloadable at runtime) YAML config

Oragono is a fork of the Ergonomadic IRC daemon <3


Go Report Card Build Status Download Latest Release Freenode #oragono Crowdin

If you want to take a look at a running Oragono instance or test some client code, feel free to play with testnet.oragono.io (TLS on port 6697 or plaintext on port 6667).


Features

  • integrated services: NickServ for user accounts, ChanServ for channel registration, and HostServ for vanity hosts
  • bouncer-like features: storing and replaying history, allowing multiple clients to use the same nickname
  • UTF-8 nick and channel names with rfc7613 (PRECIS)
  • native TLS/SSL support, including support for client certificates
  • yaml configuration
  • updating server config and TLS certificates on-the-fly (rehashing)
  • SASL authentication
  • LDAP support
  • supports multiple languages (you can also set a default language for your network)
  • advanced security and privacy features (support for requiring SASL for all logins, cloaking IPs, and running as a Tor hidden service)
  • an extensible privilege system for IRC operators
  • ident lookups for usernames
  • automated client connection limits
  • passwords stored with bcrypt
  • UBAN, a unified ban system that can target IPs, networks, masks, and registered accounts (KLINE and DLINE are also supported)
  • IRCv3 support
  • a focus on developing with specifications

Quick start guide

Download the latest release from this page: https://github.com/oragono/oragono/releases/latest

Extract it into a folder, then run the following commands:

cp default.yaml ircd.yaml
vim ircd.yaml   # modify the config file to your liking
oragono mkcerts
oragono run     # server should be ready to go!

Note: See the productionizing guide in our manual for recommendations on how to run a production network, including obtaining valid TLS certificates.

Platform Packages

Some platforms/distros also have Oragono packages maintained for them:

Using Docker

A Dockerfile and example docker-compose recipe are available in the distrib/docker directory. Oragono is automatically published to Docker Hub at oragono/oragono. For more information, see the distrib/docker README file.

From Source

You can also install this repo and use that instead! However, keep some things in mind if you go that way:

devel branches are intentionally unstable, containing fixes that may not work, and they may be rebased or reworked extensively.

The master branch should usually be stable, but may contain database changes that either have not been finalised or not had database upgrade code written yet. Don't run master on a live production network.

The stable branch contains the latest release. You can run this for a production version without any trouble.

Building

You'll need an up-to-date distribution of the Go language for your OS and architecture. Once you have that, just clone the repository and run make build. If everything goes well, you should now have an executable named oragono in the base directory of the project.

Configuration

The default config file default.yaml helps walk you through what each option means and changes.

You can use the --conf parameter when launching Oragono to control where it looks for the config file. For instance: oragono run --conf /path/to/ircd.yaml. The configuration file also stores where the log, database, certificate, and other files are opened. Normally, all these files use relative paths, but you can change them to be absolute (such as /var/log/ircd.log) when running Oragono as a service.

Logs

By default, logs go to stderr only. They can be configured to go to a file, or you can use systemd to direct the stderr to the system journal (see the manual for details). The configuration format of logs is designed to be easily pluggable, and is inspired by the logging config provided by InspIRCd.

Passwords

Passwords (for both PASS and oper logins) are stored using bcrypt. To generate encrypted strings for use in the config, use the genpasswd subcommand as such:

oragono genpasswd

With this, you receive a blob of text which you can plug into your configuration file.

Nickname and channel registration

Oragono relies heavily on user accounts to enable its distinctive features (such as allowing multiple clients per nickname). As a user, you can register your current nickname as an account using /msg NickServ register . Once you have done so, you should enable SASL in your clients, ensuring that you will be automatically logged into your account on each connection. This will prevent problems claiming your registered nickname.

Once you have registered your nickname, you can use it to register channels:

  1. Join the channel with /join #channel
  2. Register the channel with /CS REGISTER #channel

After this, your channel will remember the fact that you're the owner, the topic, and any modes set on it!

Credits

Issues
  • Running on concurrent connection larger than 2000

    Running on concurrent connection larger than 2000

    hi guys

    i'm using ergo for my chat service on mobile apps, but when it on 2000 concurrent connection the service become slowed down heavily, some user can connect after waiting 2-5 minutes, do i need to adjust config for handling this many connection.

    lovin this projects so far 👍

    opened by kingter-sutjiadi 20
  • high-availability without s2s/federation

    high-availability without s2s/federation

    #26 is going to be difficult to implement and may impact our ability to rapidly iterate on experimental IRCv3 features. Meanwhile, we know (#237) that a single oragono instance can scale to approximately 10k clients and 2k clients per channel --- enough for most teams / communities.

    Let's explore options for deploying oragono that would be highly available (i.e., resilient to server failure) while maintaining the invariant that at any given time, all clients are connected to a single server (eliminating the need for true s2s). Possible primitives:

    1. A load balancer (haproxy?) that elects a single "live" server, then directs all connections to the live server
    2. Leader election among the cluster so that only one server is "live", with the others remaining hot spares. This is Hashicorp Vault's model: https://www.vaultproject.io/docs/concepts/ha.html

    cc @eklitzke

    opened by slingamn 16
  • Option to disable message replay for a specific user.

    Option to disable message replay for a specific user.

    Hello!

    Yesterday I was working on setting up a bridge between Discord and IRC. It uses a Discord bot account, and an IRC account which is connected 24/7 to "relay" the messages. I set the message replay option to 100 messages in ergo, so new users connecting could understand the context.

    However whenever the bot reconnects to the server, all of the 100 messages get sent to the relay bot, which starts briding the messages to Discord.

    I connected to ergo's irc server yesterday, and asked if there is a command to disable this behavior for a specific user, but it seems like there isn't one implemented currently. This would be my feature request.

    Thank you for reading.

    opened by KoxSosen 14
  • Who query for opers returns all nicks

    Who query for opers returns all nicks

    When requesting the who list, using the o (oper only) parameter from rfc1459 results in returning all nicks.

    C: WHO * o
    

    If the "o" parameter is passed only operators are returned according to the name mask supplied [rfc1459]

    bug 
    opened by kylef 14
  • support LDAP

    support LDAP

    Hi,

    tl;dr Oragono could have multiple password backends, incl. PAM on UNIXes, libsasl2, or it could talk to LDAP. PAM and libsasl2 are very customizable, but just LDAP would be enough.

    PAM and libsasl2 probably require CGo to be acceptable, but hiding this code behind a build-tag is an option.


    It would be great if username+password could be checked on a backend separate from the rest.

    I run a Samba4 server to serve as a single store of user accounts (both for passwords, and for other generic user account information such as real name).

    This is, on my side, used for:

    • accounts in Prosody for XMPP,
    • accounts in Dovecot for IMAP,
    • accounts in Postfix for SMTP,
    • provide username+password portion handling for an OAuth2 server,
    • log into a Windows with it,
    • log into Gerrit
    • etc

    How?

    • Mostly things go straight into checking password via a direct LDAP bind,
    • sometimes it's LDAP bind+username lookup+actual LDAP bind for password check
    • sometimes things go through PAM towards LDAP,
    • sometimes libsasl2 + LDAP (though it could be libsasl2 + PAM + LDAP., not sure).

    Gecos fields are also populated from LDAP.

    Adding IRC to the mix would be great.

    opened by ivucica 14
  • VHost System

    VHost System

    I have no strong opinions about prioritization.

    Cloaks should:

    • Be integrated with the account registration system
    • Have no effect on server operators
    • Optionally require a server operator to create?
    opened by slingamn 13
  • Cloaks

    Cloaks

    It would be great to add the option to define a default cloak for every users, which would replace their real hostname. If I am not mistaken, this is similar to the vhost parameter for opers (?). Being able to attribute a custom cloak to an user would be even better.

    opened by lbeziaud 13
  • @draft/label tags and commands that never reply

    @draft/label tags and commands that never reply

    From #oragono:

    What's the expected behaviour when you send a @draft/label tag on a message that doesn't generate a reply (like CAP END or PONG)? The spec implies the server will send an empty batch, but Ora just ignores it.

    It's a bit nonsensical to label those, but it's a lot easier to just label all outgoing messages than figure out which are sensible things and which aren't...

    opened by csmith 12
  • oragono thrashes on large numbers of concurrent JOINs to the same channel

    oragono thrashes on large numbers of concurrent JOINs to the same channel

    I patched out DanielOaks/irc-stress-test#4 for testing purposes and observed that:

    1. connectflood scales almost linearly, which is nice
    2. Somewhere between 1024 and 4096 clients, chanflood starts to thrash on regenerateMembersCache.

    This situation may not be completely avoidable; if there are n consecutive JOINs to the same channel, we actually do have to send O(n^2) JOIN messages. But, worth looking into.

    opened by slingamn 12
  • SASL doesn't work for a grouped nick

    SASL doesn't work for a grouped nick

    With the nick eskimo registered and esk1mo as a grouped nick that that account, I can't sasl using esk1mo as the username.

    Shouldn't any grouped nick also work? I'm fairly certain most networks allow this.

    enhancement 
    opened by eskimo 11
  • Make the opers section in the config files simpler/easier to read

    Make the opers section in the config files simpler/easier to read

    Include a couple more commented-out example opers in the config file, to make it clear how real oper blocks look and how to add more, etc. Doesn't need to be anything too in-depth, just e.g.:

    opers:
        # operator named 'admin'; log in with /OPER admin [password]
        admin:
            # which capabilities this oper has access to
            class: "server-admin"
    
            # custom whois line
            whois-line: is a server admin
    
            # custom hostname
            vhost: "staff"
    
            # normally, operator status is visible to unprivileged users in WHO and WHOIS
            # responses. this can be disabled with 'hidden'. ('hidden' also causes the
            # 'vhost' line above to be ignored.)
            hidden: false
    
            # modes are modes to auto-set upon opering-up. uncomment this to automatically
            # enable snomasks ("server notification masks" that alert you to server events;
            # see `/quote help snomasks` while opered-up for more information):
            #modes: +is acjknoqtuxv
    
            # operators can be authenticated either by password (with the /OPER command),
            # or by certificate fingerprint, or both. if a password hash is set, then a
            # password is required to oper up (e.g., /OPER dan mypassword). to generate
            # the hash, use `oragono genpasswd`.
            password: "$2a$04$0123456789abcdef0123456789abcdef0123456789abcdef01234"
    
            # if a SHA-256 certificate fingerprint is configured here, then it will be
            # required to /OPER. if you comment out the password hash above, then you can
            # /OPER without a password.
            #certfp: "abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789"
            # if 'auto' is set (and no password hash is set), operator permissions will be
            # granted automatically as soon as you connect with the right fingerprint.
            #auto: true
    
        # oper named 'alice': /OPER alice [password]
        #alice:
        #    class: "network-oper"
        #    vhost: "staff/alice"
        #    password: "$2a$04$0123456789abcdef0123456789abcdef0123456789abcdef01234"
    
        # oper named 'dan': /OPER dan [password]
        #dan:
        #    class: "server-admin"
        #    vhost: "staff/dan"
        #    modes: +is acjknoqtuxv
        #    password: "$2a$04$0123456789abcdef0123456789abcdef0123456789abcdef01234"
    
    opened by DanielOaks 11
  • use new aligned atomic types everywhere

    use new aligned atomic types everywhere

    See 69448b13a10a14517 / #1969; the compiler can now ensure that a uint64 intended for atomic access is always aligned to a 64-bit boundary. Convert atomic operations on uint32s and pointers as well.

    opened by slingamn 0
  • refactor accounts system so that buntdb is no longer the data plane

    refactor accounts system so that buntdb is no longer the data plane

    This relates to #1971. In almost every place we use buntdb, it is not the data plane: it is not queried at runtime because the relevant data exists in native Go datastructures. This has the advantage that runtime latencies are not sensitive to the latency of the database layer (so we could use a much slower database layer, without impacting performance other than startup time).

    The one exception is accounts:

    • The source of truth about whether an account name is registered is buntdb
    • Account login always retrieves credentials and settings from the database

    Accounts should be refactored so they're like other systems (channel registrations, [DK]-lines, etc): the source of truth should be on the Go heap behind a sync.RWMutex, not in the database.

    opened by slingamn 0
  • Haproxy's proxy / Tor's HiddenServiceExportCircuitID

    Haproxy's proxy / Tor's HiddenServiceExportCircuitID

    This is better described at https://github.com/charybdis-ircd/charybdis/issues/267 than I can on mobile at midnight.

    It seems this was previously ripped out of Ergo https://github.com/ergochat/ergo/issues/58

    opened by Mikaela 1
  • Don't respond to TAGMSG with away replies

    Don't respond to TAGMSG with away replies

    Typing TAGMSG's cause ergo to send countless away replies as you type the message in PM to someone.

    [06:52:32]	<eskimo> ohai
    [06:52:32]	DALEK is away (Gone til 5pm)
    [06:52:32]	DALEK is away (Gone til 5pm)
    [06:52:39]	DALEK is away (Gone til 5pm)
    [06:52:41]	<eskimo> hows it goin
    [06:52:41]	DALEK is away (Gone til 5pm)
    [06:52:43]	DALEK is away (Gone til 5pm)
    [06:52:46]	DALEK is away (Gone til 5pm)
    
    opened by eskimo 0
Releases(v2.10.0)
  • v2.10.0(May 29, 2022)

    We're pleased to be publishing v2.10.0, a new stable release.

    This release contains no changes to the config file format or database file format.

    Many thanks to @csmith, @FiskFan1999, @Mikaela, @progval, and @thesamesam for contributing patches, and to @emersion, @eskimo, @FiskFan1999, @jigsy1, @Mikaela, @mogad0n, @progval, and @xnaas for reporting issues and helping test.

    Config changes

    • For better interoperability with Goguma, the recommended value of history.chathistory-maxmessages has been increased to 1000 (previously 100) (#1919)

    Changed

    • Persistent voice (AMODE +v) in a channel is now treated as a permanent invite (i.e. overriding +i on the channel) (#1901, thanks @eskimo!)
    • If you are +R, sending a direct message to an anonymous user allows them to send you replies (#1687, #1688, thanks @Mikaela and @progval!)
    • 0 is no longer valid as a nickname or account name, with a grandfather exception if it was registered on a previous version of Ergo (#1896)
    • Implemented the ratified version of the bot mode spec; the tag name is now bot instead of draft/bot (#1938)
    • Privileged WHOX on a user with multiclient shows an arbitrarily chosen client IP address, comparable to WHO (#1897)
    • SAREGISTER is allowed even under DEFCON levels 4 and lower (#1922)
    • Operators with the history capability are now exempted from time cutoff restrictions on history retrieval (#1593, #1955)

    Added

    • Added draft/read-marker capability, allowing server-side tracking of read messages for synchronization across multiple clients. (#1926, thanks @emersion!)
    • INFO now includes the server start time (#1895, thanks @xnaas!)
    • Added ACCEPT command modeled on Charybdis/Solanum, allowing +R users to whitelist users who can DM them (#1688, thanks @Mikaela!)
    • Added NS SAVERIFY for operators to manually complete an account verification (#1924, #1952, thanks @tacerus!)

    Fixed

    • Having the samode operator capability made all uses of the KICK command privileged (i.e. overriding normal channel privilege checks); this has been fixed (#1906, thanks @pcho!)
    • Fixed LIST <n always returning no results (#1934, thanks @progval and @mitchr!)
    • NickServ commands are now more clear about when a nickname is unavailable because it was previously registered and unregistered (#1886, thanks @Mikaela!)
    • Fixed KLINE'd clients producing a QUIT snotice without a corresponding CONNECT snotice (#1941, thanks @tacerus, @xnaas!)
    • Fixed incorrect handling of long/multiline 319 RPL_WHOISCHANNELS responses (#1935, thanks @Mikaela!)
    • Fixed LIST returning 403 ERR_NOSUCHCHANNEL for a nonexistent channel; the correct response is an empty list (#1928, thanks @emersion!)
    • Fixed +s ("secret") channels not appearing in LIST even when the client is already a member (#1911, #1923, thanks @jigsy1 and @FiskFan1999!)
    • Fixed a spurious success message in HISTSERV DELETE by always requiring a consistent number of parameters (#1881, #1927, thanks @FiskFan1999!)
    • Sending the empty string as a nickname would not always produce the expected error numeric 431 ERR_NONICKNAMEGIVEN; this has been fixed (#1933, #1936, thanks @kylef!)
    • znc.in/playback timestamps are now parsed as pairs of exact integers, not as floats (#1918)

    Internal

    • Upgraded to Go 1.18 (#1925)
    • Upgraded Alpine version in official Docker image
    • Fixed some issues in the example OpenRC init scripts (#1914, #1920, thanks @thesamesam!)
    Source code(tar.gz)
    Source code(zip)
    ergo-2.10.0-checksums.txt(882 bytes)
    ergo-2.10.0-checksums.txt.sig(566 bytes)
    ergo-2.10.0-freebsd-x86_64.tar.gz(3.90 MB)
    ergo-2.10.0-linux-arm64.tar.gz(3.63 MB)
    ergo-2.10.0-linux-armv6.tar.gz(3.73 MB)
    ergo-2.10.0-linux-x86_64.tar.gz(3.93 MB)
    ergo-2.10.0-macos-arm64.tar.gz(3.89 MB)
    ergo-2.10.0-macos-x86_64.tar.gz(4.02 MB)
    ergo-2.10.0-openbsd-x86_64.tar.gz(3.90 MB)
    ergo-2.10.0-plan9-x86_64.tar.gz(3.80 MB)
    ergo-2.10.0-windows-x86_64.zip(4.01 MB)
  • v2.10.0-rc2(May 23, 2022)

  • v2.10.0-rc1(May 16, 2022)

    We're pleased to be publishing the release candidate for 2.10.0 (the official release should follow in a week or so).

    This release contains no changes to the config file format or database file format.

    Many thanks to @csmith, @FiskFan1999, @Mikaela, @progval, and @thesamesam for contributing patches, and to @emersion, @eskimo, @FiskFan1999, @jigsy1, @Mikaela, @mogad0n, @progval, and @xnaas for reporting issues and helping test.

    Config changes

    • For better interoperability with Goguma, the recommended value of history.chathistory-maxmessages has been increased to 1000 (previously 100) (#1919)

    Changed

    • Persistent voice (AMODE +v) in a channel is now treated as a permanent invite (i.e. overriding +i on the channel) (#1901, thanks @eskimo!)
    • If you are +R, sending a direct message to an anonymous user allows them to send you replies (#1687, #1688, thanks @Mikaela and @progval!)
    • 0 is no longer valid as a nickname or account name, with a grandfather exception if it was registered on a previous version of Ergo (#1896)
    • Implemented the ratified version of the bot mode spec; the tag name is now bot instead of draft/bot (#1938)
    • Privileged WHOX on a user with multiclient shows an arbitrarily chosen client IP address, comparable to WHO (#1897)
    • SAREGISTER is allowed even under DEFCON levels 4 and lower (#1922)
    • Operators with the history capability are now exempted from time cutoff restrictions on history retrieval (#1593, #1955)

    Added

    • Added draft/read-marker capability, allowing server-side tracking of read messages for synchronization across multiple clients. (#1926, thanks @emersion!)
    • INFO now includes the server start time (#1895, thanks @xnaas!)
    • Added ACCEPT command modeled on Charybdis/Solanum, allowing +R users to whitelist users who can DM them (#1688, thanks @Mikaela!)
    • Added NS SAVERIFY for operators to manually complete an account verification (#1924, #1952, thanks @tacerus!)

    Fixed

    • Having the samode operator capability made all uses of the KICK command privileged (i.e. overriding normal channel privilege checks); this has been fixed (#1906, thanks @pcho!)
    • Fixed LIST <n always returning no results (#1934, thanks @progval and @mitchr!)
    • NickServ commands are now more clear about when a nickname is unavailable because it was previously registered and unregistered (#1886, thanks @Mikaela!)
    • Fixed KLINE'd clients producing a QUIT snotice without a corresponding CONNECT snotice (#1941, thanks @tacerus, @xnaas!)
    • Fixed incorrect handling of long/multiline 319 RPL_WHOISCHANNELS responses (#1935, thanks @Mikaela!)
    • Fixed LIST returning 403 ERR_NOSUCHCHANNEL for a nonexistent channel; the correct response is an empty list (#1928, thanks @emersion!)
    • Fixed +s ("secret") channels not appearing in LIST even when the client is already a member (#1911, #1923, thanks @jigsy1 and @FiskFan1999!)
    • Fixed a spurious success message in HISTSERV DELETE by always requiring a consistent number of parameters (#1881, #1927, thanks @FiskFan1999!)
    • Sending the empty string as a nickname would not always produce the expected error numeric 431 ERR_NONICKNAMEGIVEN; this has been fixed (#1933, #1936, thanks @kylef!)
    • znc.in/playback timestamps are now parsed as pairs of exact integers, not as floats (#1918)

    Internal

    • Upgraded to Go 1.18 (#1925)
    • Upgraded Alpine version in official Docker image
    • Fixed some issues in the example OpenRC init scripts (#1914, #1920, thanks @thesamesam!)
    Source code(tar.gz)
    Source code(zip)
    ergo-2.10.0-rc1-checksums.txt(918 bytes)
    ergo-2.10.0-rc1-checksums.txt.sig(566 bytes)
    ergo-2.10.0-rc1-freebsd-x86_64.tar.gz(3.90 MB)
    ergo-2.10.0-rc1-linux-arm64.tar.gz(3.63 MB)
    ergo-2.10.0-rc1-linux-armv6.tar.gz(3.73 MB)
    ergo-2.10.0-rc1-linux-x86_64.tar.gz(3.93 MB)
    ergo-2.10.0-rc1-macos-arm64.tar.gz(3.89 MB)
    ergo-2.10.0-rc1-macos-x86_64.tar.gz(4.02 MB)
    ergo-2.10.0-rc1-openbsd-x86_64.tar.gz(3.90 MB)
    ergo-2.10.0-rc1-plan9-x86_64.tar.gz(3.80 MB)
    ergo-2.10.0-rc1-windows-x86_64.zip(4.01 MB)
  • v2.9.1(Jan 10, 2022)

  • v2.9.0(Jan 9, 2022)

    We're pleased to be publishing 2.9.0, a new stable release. This release contains mostly bug fixes, with some enhancements to moderation tools.

    This release includes changes to the config file format, all of which are fully backwards-compatible and do not require updating the file before upgrading. It includes no changes to the database file format.

    Many thanks to @erincerys, @FiskFan1999, @mogad0n, and @tacerus for contributing patches, and to @ajaspers, @emersion, @FiskFan1999, @Jobe1986, @kylef, @mogad0n, @pcho, and @progval for reporting issues,

    Config changes

    • Added lock-file, which helps protect against accidentally starting multiple instances of Ergo. This is a no-op if unset. The recommended default value is ircd.lock, which (like the default datastore path ircd.db) is relative to the working directory of the Ergo process. If your datastore.path is absolute, this path (if set) should be absolute as well. (#1823)
    • +C (no channel-wide CTCP messages other than ACTION) is now a recommended default channel mode (#1851)
    • Added exempt-sasl boolean to server.ip-check-script; if enabled, IP check scripts are run only for connections without SASL, improving performance for registered users (#1888)
    • hidden: true is now the recommended default for operator definitions (#1730)

    Changed

    • The semantics of +R have been changed. +R now only prevents unauthenticated users from joining, so unregistered users who have already joined can still speak. The old semantics are still available via +RM (i.e. +R together with the +M "moderated-registered" mode). (#1858, thanks @ajaspers!)
    • Unauthenticated users matching a +I invite exception mask can now join +R channels (#1871)
    • INVITE now exempts the user from +b bans (#1876, thanks @progval!)
    • NS SUSPEND now only requires only the ban operator capability, as opposed to accreg (#1828, #1839, thanks @mogad0n!)

    Added

    • SHA-256 certificate fingerprints can now be imported from Anope and Atheme (#1864, #1869, thanks @tacerus!)
    • IP check scripts can now be run only for users that have not authenticated with SASL by the end of the handshake, improving performance for registered users (#1888)
    • Logging into an unverified account with SASL sends the new NOTE AUTHENTICATE VERIFICATION_REQUIRED standard reply code (#1852, #1853, thanks @emersion!)
    • CS PURGE now sends a snotice (#1826, thanks @tacerus!)
    • The v snomask is now used to send notifications about vhost changes initiated by operators (#1844, thanks @pcho!)

    Fixed

    • CAP LS and LIST responses after connection registration could be truncated in some cases; this has been fixed (#1872)
    • Unprivileged users with both a password and a certfp could not remove their password with NS PASSWD <password> * * as expected; this has been fixed (#1883, #1884, thanks @FiskFan1999!)
    • RELAYMSG identifiers that were not already in their case-normalized form could not be muted with +b m:; this has been fixed (#1838, thanks @mogad0n!)
    • CS AMODE changes did not take immediate effect if force-nick-equals-account was disabled and the nick did not coincide with the account; this has been fixed (#1860, thanks @eskimo!)
    • 315 RPL_ENDOFWHO now sends the exact, un-normalized mask argument provided by the client (#1831, thanks @progval!)
    • A leading $ character is now disallowed in new nicknames and account names, to avoid collision with the massmessage syntax (#1857, thanks @emersion!)
    • The deprecated o parameter of WHO now returns an empty list of results, instead of being ignored (#1730, thanks @kylef, @emersion, @progval!)
    • WHOX queries for channel oplevel now receive * instead of 0 (#1866, thanks @Jobe1986!)

    Internal

    • Updated list of official release binaries: added Apple M1, OpenBSD x86-64, and Plan 9 x86-64, removed Linux armv7, FreeBSD x86-32, and Windows x86-32. (The removed platforms are still fully supported by Ergo; you can build them from source or ask us for help.) (#1833)
    • Added an official Linux arm64 Docker image (#1855, thanks @erincerys!)
    • Added service management files for OpenSolaris/Illumos (#1846, thanks @tacerus!)
    Source code(tar.gz)
    Source code(zip)
    ergo-2.9.0-checksums.txt(873 bytes)
    ergo-2.9.0-checksums.txt.sig(566 bytes)
    ergo-2.9.0-freebsd-x86_64.tar.gz(3.80 MB)
    ergo-2.9.0-linux-arm64.tar.gz(3.49 MB)
    ergo-2.9.0-linux-armv6.tar.gz(3.52 MB)
    ergo-2.9.0-linux-x86_64.tar.gz(3.79 MB)
    ergo-2.9.0-macos-arm64.tar.gz(3.81 MB)
    ergo-2.9.0-macos-x86_64.tar.gz(3.88 MB)
    ergo-2.9.0-openbsd-x86_64.tar.gz(3.80 MB)
    ergo-2.9.0-plan9-x86_64.tar.gz(3.71 MB)
    ergo-2.9.0-windows-x86_64.zip(3.88 MB)
  • v2.9.0-rc1(Jan 2, 2022)

    [2.9.0-rc1] - 2021-01-02

    We're pleased to be publishing the release candidate for 2.9.0 (the official release should follow in a week or so).

    This release contains mostly bug fixes, with some enhancements to moderation tools.

    This release includes changes to the config file format, all of which are fully backwards-compatible and do not require updating the file before upgrading. It includes no changes to the database file format.

    Many thanks to @erincerys, @FiskFan1999, @mogad0n, and @tacerus for contributing patches, and to @ajaspers, @emersion, @FiskFan1999, @Jobe1986, @kylef, @mogad0n, @pcho, and @progval for reporting issues,

    Config changes

    • Added lock-file, which helps protect against accidentally starting multiple instances of Ergo. This is a no-op if unset. The recommended default value is ircd.lock, which (like the default datastore path ircd.db) is relative to the working directory of the Ergo process. If your datastore.path is absolute, this path (if set) should be absolute as well. (#1823)
    • +C (no channel-wide CTCP messages other than ACTION) is now a recommended default channel mode (#1851)
    • Added exempt-sasl boolean to server.ip-check-script; if enabled, IP check scripts are run only for connections without SASL, improving performance for registered users (#1888)
    • hidden: true is now the recommended default for operator definitions (#1730)

    Changed

    • The semantics of +R have been changed. +R now only prevents unauthenticated users from joining, so unregistered users who have already joined can still speak. The old semantics are still available via +RM (i.e. +R together with the +M "moderated-registered" mode). (#1858, thanks @ajaspers!)
    • Unauthenticated users matching a +I invite exception mask can now join +R channels (#1871)
    • INVITE now exempts the user from +b bans (#1876, thanks @progval!)
    • NS SUSPEND now only requires only the ban operator capability, as opposed to accreg (#1828, #1839, thanks @mogad0n!)

    Added

    • SHA-256 certificate fingerprints can now be imported from Anope and Atheme (#1864, #1869, thanks @tacerus!)
    • IP check scripts can now be run only for users that have not authenticated with SASL by the end of the handshake, improving performance for registered users (#1888)
    • Logging into an unverified account with SASL sends the new NOTE AUTHENTICATE VERIFICATION_REQUIRED standard reply code (#1852, #1853, thanks @emersion!)
    • CS PURGE now sends a snotice (#1826, thanks @tacerus!)
    • The v snomask is now used to send notifications about vhost changes initiated by operators (#1844, thanks @pcho!)

    Fixed

    • CAP LS and LIST responses after connection registration could be truncated in some cases; this has been fixed (#1872)
    • Unprivileged users with both a password and a certfp could not remove their password with NS PASSWD <password> * * as expected; this has been fixed (#1883, #1884, thanks @FiskFan1999!)
    • RELAYMSG identifiers that were not already in their case-normalized form could not be muted with +b m:; this has been fixed (#1838, thanks @mogad0n!)
    • CS AMODE changes did not take immediate effect if force-nick-equals-account was disabled and the nick did not coincide with the account; this has been fixed (#1860, thanks @eskimo!)
    • 315 RPL_ENDOFWHO now sends the exact, un-normalized mask argument provided by the client (#1831, thanks @progval!)
    • A leading $ character is now disallowed in new nicknames and account names, to avoid collision with the massmessage syntax (#1857, thanks @emersion!)
    • The deprecated o parameter of WHO now returns an empty list of results, instead of being ignored (#1730, thanks @kylef, @emersion, @progval!)
    • WHOX queries for channel oplevel now receive * instead of 0 (#1866, thanks @Jobe1986!)

    Internal

    • Updated list of official release binaries: added Apple M1, OpenBSD x86-64, and Plan 9 x86-64, removed Linux armv7, FreeBSD x86-32, and Windows x86-32. (The removed platforms are still fully supported by Ergo; you can build them from source or ask us for help.) (#1833)
    • Added an official Linux arm64 Docker image (#1855, thanks @erincerys!)
    • Added service management files for OpenSolaris/Illumos (#1846, thanks @tacerus!)
    Source code(tar.gz)
    Source code(zip)
    ergo-2.9.0-rc1-checksums.txt(909 bytes)
    ergo-2.9.0-rc1-checksums.txt.sig(566 bytes)
    ergo-2.9.0-rc1-freebsd-x86_64.tar.gz(3.80 MB)
    ergo-2.9.0-rc1-linux-arm64.tar.gz(3.49 MB)
    ergo-2.9.0-rc1-linux-armv6.tar.gz(3.53 MB)
    ergo-2.9.0-rc1-linux-x86_64.tar.gz(3.79 MB)
    ergo-2.9.0-rc1-macos-arm64.tar.gz(3.81 MB)
    ergo-2.9.0-rc1-macos-x86_64.tar.gz(3.88 MB)
    ergo-2.9.0-rc1-openbsd-x86_64.tar.gz(3.80 MB)
    ergo-2.9.0-rc1-plan9-x86_64.tar.gz(3.71 MB)
    ergo-2.9.0-rc1-windows-x86_64.zip(3.88 MB)
  • v2.8.0(Nov 14, 2021)

    We're pleased to be publishing Ergo 2.8.0. This release contains many fixes and enhancements, plus one major user-facing feature: user-initiated password resets via e-mail (#734).

    This release includes changes to the config file format, all of which are fully backwards-compatible and do not require updating the file before upgrading.

    This release includes a database change. If you have datastore.autoupgrade set to true in your configuration, it will be automatically applied when you restart Ergo. Otherwise, you can update the database manually by running ergo upgradedb (see the manual for complete instructions).

    As part of this release, our official Docker images have moved from Docker Hub to the GitHub Container Registry, at ghcr.io/ergochat/ergo. The stable and master tags correspond to the respective branches. Tagged releases (e.g. v2.8.0) are available under the corresponding named tags.

    Many thanks to @ajaspers, @delthas, @mogad0n, @majiru, @ProgVal, and @tacerus for contributing patches, to @ajaspers for contributing code review, to @ajaspers, @cxxboy, @dallemon, @emersion, @erikh, @eskimo, @jwheare, @kylef, @Mikaela, @mogad0n, @MystaraTheGreat, @ProgVal, @tacerus, @tamiko, and @xnaas for reporting issues and helping test, and to our translators for contributing translations.

    Config changes

    • Added accounts.registration.email-verification.password-reset block to configure e-mail-based password reset (#734, #1779)
    • Added accounts.registration.email-verification.timeout to impose a timeout on e-mail sending; the recommended default value is 60s (60 seconds) (#1741)
    • Added server.suppress-lusers to allow hiding the LUSERS counts (#1802, thanks @eskimo!)

    Security

    • Added accounts.registration.email-verification.timeout to impose a timeout on e-mail sending; the recommended default value is 60s (60 seconds) (#1741)

    Added

    • Added user-initiated password resets via email (#734). This requires e-mail verification of accounts, and must additionally be enabled explicitly: see the email-verification block in default.yaml for more information.
    • Added the draft/extended-monitor capability (#1761, thanks @delthas!)
    • When doing direct sending of verification emails, make email delivery failures directly visible to the end user (#1659, #1741, thanks @tacerus!)
    • For operators, NS INFO now shows the user's email address (you can also view your own address) (#1677, thanks @ajaspers!)
    • Operators with the appropriate permissions will now see IPs in /WHOWAS output (#1702, thanks @ajaspers!)
    • Added the +s d snomask, for operators to receive information about session disconnections that do not result in a full QUIT (#1709, #1728, thanks @mogad0n!)
    • Added support for the SCRAM-SHA-256 SASL authentication mechanism (#175). This mechanism is not currently advertised in CAP LS output because IRCCloud handles it incorrectly. We also recommend against using SCRAM because of its lack of genuine security benefits.
    • /UBAN LIST output now includes the time the ban was created (#1725, #1755, thanks @Mikaela and @mogad0n!)
    • Added support for running as a Type=notify systemd service (#1733)
    • Added a warning to help users detect incorrect uses of /QUOTE (#1530)

    Fixed

    • The +M (only registered users can speak) channel mode did not work; this has been fixed (#1696, thanks @Mikaela!)
    • A channel /RENAME that only changed the case of the channel would delete the channel registration; this has been fixed (#1751, thanks @Mikaela!)
    • Fixed allow-truncation: true not actually allowing truncation of overlong lines (#1766, thanks @tacerus!)
    • Fixed several pagination bugs in CHATHISTORY (#1676, thanks @emersion!)
    • Fixed support for kicking multiple users from a channel on the same line, the TARGMAX 005 parameter that advertises this, and the default kick message (#1748, #1777, #1776), thanks @ProgVal!)
    • Fixed /SAMODE on a channel not producing a snomask (#1787, thanks @mogad0n, @ajaspers!)
    • Adding +f to a channel with SAMODE used to require channel operator privileges on the receiving channel; this has been fixed (#1825, thanks @Mikaela!)
    • Fixed parameters sent with 697 ERR_LISTMODEALREADYSET and 698 ERR_LISTMODENOTSET (#1727, thanks @kylef!)
    • Fixed parameter sent with 696 ERR_INVALIDMODEPARAM (#1773, thanks @kylef!)
    • Fixed handling of channel mode +k with an empty parameter (#1774, #1775, thanks @ProgVal!)
    • WHOWAS with an empty string as the parameter now produces an appropriate error response (#1703, thanks @kylef!)
    • Fixed error response to an empty realname on the USER line (#1778, thanks @ProgVal!)
    • Fixed /UBAN ADD of a NUH mask (i.e. a k-line) not killing affected clients (#1736, thanks @mogad0n!)
    • Fixed buggy behavior when +i is configured as a default mode for channels (#1756, thanks @Mikaela!)
    • Fixed issues with channels.operator-only-creation not respecting /SAJOIN or always-on clients (#1757)
    • Protocol-breaking operator vhosts are now disallowed during config validation (#1722)
    • Fixed error message associated with /NS PASSWD on a nonexistent account (#1738, thanks @Mikaela!)
    • Fixed an incorrect CHATHISTORY fail message (#1731, thanks @ProgVal!)
    • Fixed a panic on an invalid configuration case (#1714, thanks @erikh!)

    Changed

    • Upgraded the draft/register capability to the latest draft/account-registration iteration (#1740)
    • Unregistered users with +v or higher can now speak in +R (registered-only) channels (#1715, thanks @Mikaela and @ajaspers!)
    • For always-on clients with at least one active connection, 338 RPL_WHOISACTUALLY now displays an arbitrarily chosen client IP address (#1650, thanks @MystaraTheGreat!)
    • # can no longer be used in new account names and nicknames, or as the RELAYMSG separator (#1679)
    • The oragono.io/nope capability was renamed to ergo.chat/nope (#1793)

    Removed

    • never is no longer accepted as a value of the replay-joins NickServ setting (/NS SET replay-joins); user accounts which enabled this setting have been reverted to the default value of commands-only (#1676)

    Internal

    • We have a cool new logo!
    • Official builds now use Go 1.17 (#1781)
    • Official Docker containers are now at ghcr.io/ergochat/ergo (#1808)
    • Added a traditional SysV init script (#1691, thanks @tacerus!)
    • Added an s6 init script (#1786, thanks @majiru!)
    Source code(tar.gz)
    Source code(zip)
    ergo-2.8.0-checksums.txt(960 bytes)
    ergo-2.8.0-freebsd-386.tar.gz(3.52 MB)
    ergo-2.8.0-freebsd-x86_64.tar.gz(3.79 MB)
    ergo-2.8.0-linux-386.tar.gz(3.53 MB)
    ergo-2.8.0-linux-arm64.tar.gz(3.48 MB)
    ergo-2.8.0-linux-armv6.tar.gz(3.52 MB)
    ergo-2.8.0-linux-armv7.tar.gz(3.51 MB)
    ergo-2.8.0-linux-x86_64.tar.gz(3.78 MB)
    ergo-2.8.0-macos-x86_64.tar.gz(3.87 MB)
    ergo-2.8.0-windows-386.zip(3.72 MB)
    ergo-2.8.0-windows-x86_64.zip(3.87 MB)
  • v2.8.0-rc1(Nov 3, 2021)

    We're pleased to be publishing the release candidate for 2.8.0 (the official release should follow in a week or so).

    This release contains many fixes and enhancements, plus one major user-facing feature: user-initiated password resets via e-mail (#734).

    This release includes changes to the config file format, all of which are fully backwards-compatible and do not require updating the file before upgrading.

    This release includes a database change. If you have datastore.autoupgrade set to true in your configuration, it will be automatically applied when you restart Ergo. Otherwise, you can update the database manually by running ergo upgradedb (see the manual for complete instructions).

    As part of this release, our official Docker images will move from Docker Hub to the GitHub Container Registry at ghcr.io; more details will be forthcoming with the final release.

    Many thanks to @ajaspers, @delthas, @mogad0n, @majiru, @ProgVal, and @tacerus for contributing patches, to @ajaspers for contributing code review, to @ajaspers, @cxxboy, @dallemon, @emersion, @erikh, @eskimo, @jwheare, @kylef, @Mikaela, @mogad0n, @MystaraTheGreat, @ProgVal, @tacerus, @tamiko, and @xnaas for reporting issues and helping test, and to our translators for contributing translations.

    Config changes

    • Added accounts.registration.email-verification.password-reset block to configure e-mail-based password reset (#734, #1779)
    • Added accounts.registration.email-verification.timeout to impose a timeout on e-mail sending; the recommended default value is 60s (60 seconds) (#1741)
    • Added server.suppress-lusers to allow hiding the LUSERS counts (#1802, thanks @eskimo!)

    Security

    • Added accounts.registration.email-verification.timeout to impose a timeout on e-mail sending; the recommended default value is 60s (60 seconds) (#1741)

    Added

    • Added user-initiated password resets via email (#734). This requires e-mail verification of accounts, and must additionally be enabled explicitly: see the email-verification block in default.yaml for more information.
    • Added the draft/extended-monitor capability (#1761, thanks @delthas!)
    • When doing direct sending of verification emails, make email delivery failures directly visible to the end user (#1659, #1741, thanks @tacerus!)
    • For operators, NS INFO now shows the user's email address (you can also view your own address) (#1677, thanks @ajaspers!)
    • Operators with the appropriate permissions will now see IPs in /WHOWAS output (#1702, thanks @ajaspers!)
    • Added the +s d snomask, for operators to receive information about session disconnections that do not result in a full QUIT (#1709, #1728, thanks @mogad0n!)
    • Added support for the SCRAM-SHA-256 SASL authentication mechanism (#175). This mechanism is not currently advertised in CAP LS output because IRCCloud handles it incorrectly. We also recommend against using SCRAM because of its lack of genuine security benefits.
    • /UBAN LIST output now includes the time the ban was created (#1725, #1755, thanks @Mikaela and @mogad0n!)
    • Added support for running as a Type=notify systemd service (#1733)
    • Added a warning to help users detect incorrect uses of /QUOTE (#1530)

    Fixed

    • The +M (only registered users can speak) channel mode did not work; this has been fixed (#1696, thanks @Mikaela!)
    • A channel /RENAME that only changed the case of the channel would delete the channel registration; this has been fixed (#1751, thanks @Mikaela!)
    • Fixed allow-truncation: true not actually allowing truncation of overlong lines (#1766, thanks @tacerus!)
    • Fixed several pagination bugs in CHATHISTORY (#1676, thanks @emersion!)
    • Fixed support for kicking multiple users from a channel on the same line, the TARGMAX 005 parameter that advertises this, and the default kick message (#1748, #1777, #1776), thanks @ProgVal!)
    • Fixed /SAMODE on a channel not producing a snomask (#1787, thanks @mogad0n, @ajaspers!)
    • Fixed parameters sent with 697 ERR_LISTMODEALREADYSET and 698 ERR_LISTMODENOTSET (#1727, thanks @kylef!)
    • Fixed parameter sent with 696 ERR_INVALIDMODEPARAM (#1773, thanks @kylef!)
    • Fixed handling of channel mode +k with an empty parameter (#1774, #1775, thanks @ProgVal!)
    • WHOWAS with an empty string as the parameter now produces an appropriate error response (#1703, thanks @kylef!)
    • Fixed error response to an empty realname on the USER line (#1778, thanks @ProgVal!)
    • Fixed /UBAN ADD of a NUH mask (i.e. a k-line) not killing affected clients (#1736, thanks @mogad0n!)
    • Fixed buggy behavior when +i is configured as a default mode for channels (#1756, thanks @Mikaela!)
    • Fixed issues with channels.operator-only-creation not respecting /SAJOIN or always-on clients (#1757)
    • Protocol-breaking operator vhosts are now disallowed during config validation (#1722)
    • Fixed error message associated with /NS PASSWD on a nonexistent account (#1738, thanks @Mikaela!)
    • Fixed an incorrect CHATHISTORY fail message (#1731, thanks @ProgVal!)
    • Fixed a panic on an invalid configuration case (#1714, thanks @erikh!)

    Changed

    • Upgraded the draft/register capability to the latest draft/account-registration iteration (#1740)
    • Unregistered users with +v or higher can now speak in +R (registered-only) channels (#1715, thanks @Mikaela and @ajaspers!)
    • For always-on clients with at least one active connection, 338 RPL_WHOISACTUALLY now displays an arbitrarily chosen client IP address (#1650, thanks @MystaraTheGreat!)
    • # can no longer be used in new account names and nicknames, or as the RELAYMSG separator (#1679)
    • The oragono.io/nope capability was renamed to ergo.chat/nope (#1793)

    Internal

    • We have a cool new logo!
    • Official builds now use Go 1.17 (#1781)
    • Official Docker containers are now at ghcr.io/ergochat/ergo (#1808)
    • Added a traditional SysV init script (#1691, thanks @tacerus!)
    • Added an s6 init script (#1786, thanks @majiru!)
    Source code(tar.gz)
    Source code(zip)
    ergo-2.8.0-rc1-checksums.txt(1000 bytes)
    ergo-2.8.0-rc1-freebsd-386.tar.gz(3.52 MB)
    ergo-2.8.0-rc1-freebsd-x86_64.tar.gz(3.79 MB)
    ergo-2.8.0-rc1-linux-386.tar.gz(3.53 MB)
    ergo-2.8.0-rc1-linux-arm64.tar.gz(3.48 MB)
    ergo-2.8.0-rc1-linux-armv6.tar.gz(3.51 MB)
    ergo-2.8.0-rc1-linux-armv7.tar.gz(3.51 MB)
    ergo-2.8.0-rc1-linux-x86_64.tar.gz(3.78 MB)
    ergo-2.8.0-rc1-macos-x86_64.tar.gz(3.87 MB)
    ergo-2.8.0-rc1-windows-386.zip(3.72 MB)
    ergo-2.8.0-rc1-windows-x86_64.zip(3.87 MB)
  • v2.7.0(Jun 8, 2021)

    We're pleased to be publishing Ergo 2.7.0, our first official release under our new name of Ergo. This release contains bug fixes and minor enhancements.

    This release includes changes to the config file format, all of which are fully backwards-compatible and do not require updating the file before upgrading. This release includes no changes to the database format.

    Because the name of the executable has changed from oragono to ergo (ergo.exe on Windows), you may need to update your system configuration (e.g., scripts or systemd unit files that reference the executable).

    Many thanks to @ajaspers and @jesopo for contributing patches, to @ajaspers, @ChrisTX, @emersion, @jwheare, @kylef, @Mikaela, @mogad0n, and @ProgVal for reporting issues and helping test, and to our translators for contributing translations.

    Changed

    • The project was renamed from "Oragono" to "Ergo" (#897, thanks to everyone who contributed feedback or voted in the poll)

    Config changes

    • Entries in server.listeners now take a new key, min-tls-version, that can be used to set the minimum required TLS version; the recommended default value is 1.2 (#1611, thanks @ChrisTX!)
    • Added max-conns (maximum connection count) and max-conn-lifetime (maximum lifetime of a connection before it is cycled) to datastore.mysql (#1622)
    • Added massmessage operator capability to allow sending NOTICEs to all connected users (#1153, #1629, thanks @jesopo!)

    Security

    • If require-sasl.enabled is set to true, tor-listeners.require-sasl will be automatically set to true as well (#1636)
    • It is now possible to set the minimum required TLS version, using the min-tls-version key in listener configuration
    • Configurations that require SASL but allow user registration now produce a warning (#1637)

    Added:

    • Operators with the correct permissions can now send "mass messages", e.g. /NOTICE $$* will send a NOTICE to all users (#1153, #1629, thanks @jesopo!)
    • Operators can now extend the maximum (non-tags) length of the IRC line using the server.max-line-len configuration key. This is not recommended for use outside of "closed-circuit" deployments where IRC operators have full control of all client software. (#1651)

    Fixed

    • RELAYMSG now sends a full NUH ("nick-user-host"), instead of only the relay nickname, as the message source (#1647, thanks @ProgVal, @jwheare, and @Mikaela!)
    • Fixed a case where channels would remain visible in /LIST after unregistration (#1619, thanks @ajaspers!)
    • Fixed incorrect tags on JOIN lines in +u ("auditorium") channels (#1642)
    • Fixed an issue where LUSERS counts could get out of sync (#1617)
    • It was impossible to add a restricted set of snomasks to an operator's permissions; this has been fixed (#1618)
    • Fixed incorrect language in NS INFO responses (#1627, thanks @ajaspers!)
    • Fixed a case where the REGISTER command would emit an invalid error message (#1633, thanks @ajaspers!)
    • Fixed snomasks displaying in a nondeterministic order (#1669, thanks @Mikaela!)

    Removed

    • Removed the draft/resume-0.5 capability, and the associated RESUME and BRB commands (#1624)

    Internal

    • Optimized MySQL storage of direct messages (#1615)
    Source code(tar.gz)
    Source code(zip)
    ergo-2.7.0-checksums.txt(960 bytes)
    ergo-2.7.0-freebsd-386.tar.gz(3.61 MB)
    ergo-2.7.0-freebsd-x86_64.tar.gz(3.81 MB)
    ergo-2.7.0-linux-386.tar.gz(3.62 MB)
    ergo-2.7.0-linux-arm64.tar.gz(3.49 MB)
    ergo-2.7.0-linux-armv6.tar.gz(3.59 MB)
    ergo-2.7.0-linux-armv7.tar.gz(3.58 MB)
    ergo-2.7.0-linux-x86_64.tar.gz(3.83 MB)
    ergo-2.7.0-macos-x86_64.tar.gz(3.92 MB)
    ergo-2.7.0-windows-386.zip(3.82 MB)
    ergo-2.7.0-windows-x86_64.zip(3.93 MB)
  • v2.7.0-rc1(May 31, 2021)

    We're pleased to be publishing Ergo 2.7.0-rc1, our first release candidate under our new name of Ergo. This release contains bug fixes and minor enhancements.

    This release includes changes to the config file format, all of which are fully backwards-compatible and do not require updating the file before upgrading. This release includes no changes to the database format.

    Because the name of the executable has changed from oragono to ergo (ergo.exe on Windows), you may need to update your system configuration (e.g., scripts or systemd unit files that reference the executable).

    Many thanks to @ajaspers and @jesopo for contributing patches, to @ajaspers, @ChrisTX, @emersion, @jwheare, @kylef, @Mikaela, @mogad0n, and @ProgVal for reporting issues and helping test, and to our translators for contributing translations.

    Changed

    • The project was renamed from "Oragono" to "Ergo" (#897, thanks to everyone who contributed feedback or voted in the poll)

    Config changes

    • Entries in server.listeners now take a new key, min-tls-version, that can be used to set the minimum required TLS version; the recommended default value is 1.2 (#1611, thanks @ChrisTX!)
    • Added max-conns (maximum connection count) and max-conn-lifetime (maximum lifetime of a connection before it is cycled) to datastore.mysql (#1622)
    • Added massmessage operator capability to allow sending NOTICEs to all connected users (#1153, #1629, thanks @jesopo!)

    Security

    • If require-sasl.enabled is set to true, tor-listeners.require-sasl will be automatically set to true as well (#1636)
    • It is now possible to set the minimum required TLS version, using the min-tls-version key in listener configuration
    • Configurations that require SASL but allow user registration now produce a warning (#1637)

    Added:

    • Operators with the correct permissions can now send "mass messages", e.g. /NOTICE $$* will send a NOTICE to all users (#1153, #1629, thanks @jesopo!)
    • Operators can now extend the maximum (non-tags) length of the IRC line using the server.max-line-len configuration key. This is not recommended for use outside of "closed-circuit" deployments where IRC operators have full control of all client software. (#1651)

    Fixed

    • RELAYMSG now sends a full NUH ("nick-user-host"), instead of only the relay nickname, as the message source (#1647, thanks @ProgVal, @jwheare, and @Mikaela!)
    • Fixed a case where channels would remain visible in /LIST after unregistration (#1619, thanks @ajaspers!)
    • Fixed incorrect tags on JOIN lines in +u ("auditorium") channels (#1642)
    • Fixed an issue where LUSERS counts could get out of sync (#1617)
    • It was impossible to add a restricted set of snomasks to an operator's permissions; this has been fixed (#1618)
    • Fixed incorrect language in NS INFO responses (#1627, thanks @ajaspers!)
    • Fixed a case where the REGISTER command would emit an invalid error message (#1633, thanks @ajaspers!)
    • Fixed snomasks displaying in a nondeterministic order (#1669, thanks @Mikaela!)

    Removed

    • Removed the draft/resume-0.5 capability, and the associated RESUME and BRB commands (#1624)

    Internal

    • Optimized MySQL storage of direct messages (#1615)
    Source code(tar.gz)
    Source code(zip)
    ergo-2.7.0-rc1-checksums.txt(1000 bytes)
    ergo-2.7.0-rc1-freebsd-386.tar.gz(3.61 MB)
    ergo-2.7.0-rc1-freebsd-x86_64.tar.gz(3.81 MB)
    ergo-2.7.0-rc1-linux-386.tar.gz(3.62 MB)
    ergo-2.7.0-rc1-linux-arm64.tar.gz(3.49 MB)
    ergo-2.7.0-rc1-linux-armv6.tar.gz(3.59 MB)
    ergo-2.7.0-rc1-linux-armv7.tar.gz(3.58 MB)
    ergo-2.7.0-rc1-linux-x86_64.tar.gz(3.83 MB)
    ergo-2.7.0-rc1-macos-x86_64.tar.gz(3.92 MB)
    ergo-2.7.0-rc1-windows-386.zip(3.82 MB)
    ergo-2.7.0-rc1-windows-x86_64.zip(3.93 MB)
  • v2.6.1(Apr 26, 2021)

    Oragono 2.6.1 is a bugfix release, fixing a security issue that is critical for some private server configurations. We regret the oversight.

    The issue affects two classes of server configuration:

    1. Private servers that use server.password (i.e., the PASS command) for protection. If accounts.registration.allow-before-connect is enabled, the REGISTER command can be used to bypass authentication. Affected operators should set this field to false, or upgrade to 2.6.1, which disallows the insecure configuration. (If the field does not appear in the configuration file, the configuration is secure since the value defaults to false when unset.)
    2. Private servers that use accounts.require-sasl for protection. If these servers do not additionally set accounts.registration.enabled to false, the REGISTER command can potentially be used to bypass authentication. Affected operators should set accounts.registration.enabled to false; this recommendation appeared in the operator manual but was not emphasized sufficiently. (Configurations that require SASL but allow open registration are potentially valid, e.g., in the case of public servers that require everyone to use a registered account; accordingly, Oragono 2.6.1 continues to permit such configurations.)

    This release includes no changes to the config file format or the database.

    Many thanks to @ajaspers for reporting the issue.

    Security

    • Fixed and documented potential authentication bypasses via the REGISTER command (#1634, thanks [@ajaspers](https:// github.com/ajaspers)!)
    Source code(tar.gz)
    Source code(zip)
    oragono-2.6.1-checksums.txt(990 bytes)
    oragono-2.6.1-freebsd-386.tar.gz(3.62 MB)
    oragono-2.6.1-freebsd-x86_64.tar.gz(3.81 MB)
    oragono-2.6.1-linux-386.tar.gz(3.62 MB)
    oragono-2.6.1-linux-arm64.tar.gz(3.49 MB)
    oragono-2.6.1-linux-armv6.tar.gz(3.59 MB)
    oragono-2.6.1-linux-armv7.tar.gz(3.59 MB)
    oragono-2.6.1-linux-x86_64.tar.gz(3.83 MB)
    oragono-2.6.1-macos-x86_64.tar.gz(3.92 MB)
    oragono-2.6.1-windows-386.zip(3.82 MB)
    oragono-2.6.1-windows-x86_64.zip(3.93 MB)
  • v2.6.0(Apr 18, 2021)

    We're pleased to announce Oragono 2.6.0, a new stable release.

    This release has some user-facing enhancements, but is primarily focused on fixing bugs and advancing the state of IRCv3 standardization (by publishing a release that implements the latest drafts). Some highlights:

    • A new CHATHISTORY API for listing direct message conversations (#1592)
    • The latest proposal for IRC-over-websockets, which should be backwards-compatible with existing clients (#1558)
    • The latest specification for the bot usermode (+B in our implementation) (#1562)

    This release includes changes to the config file format, all of which are fully backwards-compatible and do not require updating the file before upgrading.

    This release includes no changes to the embedded database format. If you are using MySQL for history storage, it adds a new table; this change is backwards and forwards-compatible and does not require any manual intervention.

    If you are using nginx as a reverse proxy for IRC-over-websockets, previous documentation did not recommend increasing proxy_read_timeout; the default value of 60s is too low and can lead to user disconnections. The current recommended value is proxy_read_timeout 600s;; see the manual for an example configuration.

    Many thanks to @ajaspers and @Mikaela for contributing patches, to @aster1sk, @emersion, @eskimo, @hhirtz, @jlu5, @jwheare, @KoraggKnightWolf, @kylef, @Mikaela, @mogad0n, @ProgVal, and @szlend for reporting issues and helping test, and to our translators for contributing translations.

    Config changes

    • Listeners now support multiple TLS certificates for use with SNI; see the manual for details (#875, thanks @Mikaela!)
    • Added server.compatibility.allow-truncation, controlling whether the server accepts messages that are too long to be relayed intact; this value defaults to true when unset (#1577, #1586, thanks @kylef!)
    • Added new snomasks operator capability; operators must have either the ban or snomasks capability to subscribe to additional snomasks (#1176)

    Security

    • Fixed several edge cases where Oragono might relay invalid UTF8 despite the UTF8ONLY guarantee, or to a text-mode websocket client (#1575, #1596, thanks @ProgVal!)
    • All operator privilege checks now use the capabilities system, making it easier to define operators with restricted powers (#1176)
    • Adding and removing bans with UBAN now produces snomasks and audit loglines (#1518, thanks @mogad0n!)

    Fixed

    • Fixed an edge case in line buffering that could result in client disconnections (#1572, thanks @ProgVal!)
    • Upgraded buntdb, our embedded database library, fixing an edge case that could cause data corruption (#1603, thanks @Mikaela, @tidwall!)
    • Improved compatibility with the published draft/register specification (#1568, thanks @ProgVal!)
    • 433 ERR_NICKNAMEINUSE is no longer sent when a fully connected ("registered") client fails to claim a reserved nickname, fixing a bad interaction with some client software (#1594, thanks @ProgVal!)
    • Fixed znc.in/playback commands causing client disconnections when history is disabled (#1552, thanks @szlend!)
    • Fixed syntactically invalid 696 ERR_INVALIDMODEPARAM response for invalid channel keys (#1563, thanks @ProgVal!)
    • User-set nickserv settings now display as "enabled" instead of "mandatory" (#1544, thanks @Mikaela!)
    • Improved error messages for some invalid configuration cases (#1559, thanks @aster1sk!)
    • Improved CS TRANSFER error messages (#1534, thanks burning!)
    • Handle panics caused when rehashing with SIGHUP (#1570)

    Changed

    • Registered channels will always appear in /LIST output, even with no members (#1507)
    • In the new recommended default configuration, Oragono will preemptively reject messages that are too long to be relayed to clients without truncation. This is controlled by the config variable server.compatibility.allow-truncation; this field defaults to true when unset, preserving the legacy behavior for older config files (#1577, #1586, thanks @kylef!)
    • Auto-away behavior now respects individual clients; the user is not considered away unless all clients are away or disconnected (#1531, thanks @kylef!)
    • Direct messages rejected due to the +R registered-only usermode now produce an error message (#1064, thanks @KoraggKnightWolf, @ajaspers!)
    • RELAYMSG identifiers now respect bans and mutes (#1502)
    • If end user message deletion is enabled, channel operators can now delete channel messages (#1565, thanks @Mikaela!)
    • Halfops can change the channel topic (#1523)
    • Snomask add/remove syntax now matches other ircds more closely (#1074)
    • CS OP will regrant your channel AMODE, in case you removed it (#1516, #1307, thanks @jlu5!)
    • User passwords may no longer begin with : (#1571)
    • Improved documentation of CS AMODE and NS UNREGISTER (#1524, #1545, thanks @Mikaela!)
    • Disabling history disables history-related CAPs (#1549)

    Added

    • Implemented the new CHATHISTORY TARGETS API for listing direct message conversations (#1592, thanks @emersion, @hhirtz, @jwheare, @kylef!)
    • Implemented the new IRC-over-websockets draft, adding support for binary websockets and subprotocol negotiation (#1558, thanks @jwheare!)
    • Implemented the new bot mode spec (#1562)
    • Implemented the new forward mode spec (#1612, thanks @ProgVal!)
    • WARN NICK ACCOUNT_REQUIRED is sent on failed attempts to claim a reserved nickname (#1594)
    • NS CLIENTS LIST displays enabled client capabilities (#1576)
    • CS INFO with no arguments lists your registered channels (#765)
    • NS PASSWORD is now accepted as an alias for NS PASSWD (#1547)

    Internal

    • Upgraded to Go 1.16 (#1510)
    Source code(tar.gz)
    Source code(zip)
    oragono-2.6.0-checksums.txt(990 bytes)
    oragono-2.6.0-freebsd-386.tar.gz(3.61 MB)
    oragono-2.6.0-freebsd-x86_64.tar.gz(3.81 MB)
    oragono-2.6.0-linux-386.tar.gz(3.62 MB)
    oragono-2.6.0-linux-arm64.tar.gz(3.49 MB)
    oragono-2.6.0-linux-armv6.tar.gz(3.59 MB)
    oragono-2.6.0-linux-armv7.tar.gz(3.59 MB)
    oragono-2.6.0-linux-x86_64.tar.gz(3.83 MB)
    oragono-2.6.0-macos-x86_64.tar.gz(3.92 MB)
    oragono-2.6.0-windows-386.zip(3.82 MB)
    oragono-2.6.0-windows-x86_64.zip(3.93 MB)
  • v2.6.0-rc1(Apr 11, 2021)

    We're pleased to be publishing the release candidate for 2.6.0 (the official release should follow in a week or so).

    This release has some user-facing enhancements, but is primarily focused on fixing bugs and advancing the state of IRCv3 standardization (by publishing a release that implements the latest drafts). Some highlights:

    • A new CHATHISTORY API for listing direct message conversations (#1592)
    • The latest proposal for IRC-over-websockets, which should be backwards-compatible with existing clients (#1558)
    • The latest specification for the bot usermode (+B in our implementation) (#1562)

    This release includes changes to the config file format, all of which are fully backwards-compatible and do not require updating the file before upgrading.

    This release includes no changes to the embedded database format. If you are using MySQL for history storage, it adds a new table; this change is backwards and forwards-compatible and does not require any manual intervention.

    If you are using nginx as a reverse proxy for IRC-over-websockets, previous documentation did not recommend increasing proxy_read_timeout; the default value of 60s is too low and can lead to user disconnections. The current recommended value is proxy_read_timeout 600s;; see the manual for an example configuration.

    Many thanks to @ajaspers and @Mikaela for contributing patches, to @aster1sk, @emersion, @eskimo, @hhirtz, @jlu5, @jwheare, @KoraggKnightWolf, @kylef, @Mikaela, @mogad0n, @ProgVal, and @szlend for reporting issues and helping test, and to our translators for contributing translations.

    Config changes

    • Listeners now support multiple TLS certificates for use with SNI; see the manual for details (#875, thanks @Mikaela!)
    • Added server.compatibility.allow-truncation, controlling whether the server accepts messages that are too long to be relayed intact; this value defaults to true when unset (#1596, thanks @kylef!)
    • Added new snomasks operator capability; operators must have either the ban or snomasks capability to subscribe to additional snomasks (#1176)

    Security

    • Fixed several edge cases where Oragono might relay invalid UTF8 despite the UTF8ONLY guarantee, or to a text-mode websocket client (#1575, #1596, thanks @ProgVal!)
    • All operator privilege checks now use the capabilities system, making it easier to define operators with restricted powers (#1176)
    • Adding and removing bans with UBAN now produces snomasks and audit loglines (#1518, thanks @mogad0n!)

    Fixed

    • Fixed an edge case in line buffering that could result in client disconnections (#1572, thanks @ProgVal!)
    • Upgraded buntdb, our embedded database library, fixing an edge case that could cause data corruption (#1603, thanks @Mikaela, @tidwall!)
    • Improved compatibility with the published draft/register specification (#1568, thanks @ProgVal!)
    • 433 ERR_NICKNAMEINUSE is no longer sent when a fully connected ("registered") client fails to claim a reserved nickname, fixing a bad interaction with some client software (#1594, thanks @ProgVal!)
    • Fixed znc.in/playback commands causing client disconnections when history is disabled (#1552, thanks @szlend!)
    • Fixed syntactically invalid 696 ERR_INVALIDMODEPARAM response for invalid channel keys (#1563, thanks @ProgVal!)
    • User-set nickserv settings now display as "enabled" instead of "mandatory" (#1544, thanks @Mikaela!)
    • Improved error messages for some invalid configuration cases (#1559, thanks @aster1sk!)
    • Improved CS TRANSFER error messages (#1534, thanks burning!)
    • Handle panics caused when rehashing with SIGHUP (#1570)

    Changed

    • Registered channels will always appear in /LIST output, even with no members (#1507)
    • In the new recommended default configuration, Oragono will preemptively reject messages that are too long to be relayed to clients without truncation. This is controlled by the config variable server.compatibility.allow-truncation; this field defaults to true when unset, preserving the legacy behavior for older config files (#1577, #1586, thanks @kylef!)
    • Auto-away behavior now respects individual clients; the user is not considered away unless all clients are away or disconnected (#1531, thanks @kylef!)
    • Direct messages rejected due to the +R registered-only usermode now produce an error message (#1064, thanks @KoraggKnightWolf, @ajaspers!)
    • RELAYMSG identifiers now respect bans and mutes (#1502)
    • If end user message deletion is enabled, channel operators can now delete channel messages (#1565, thanks @Mikaela!)
    • Halfops can change the channel topic (#1523)
    • Snomask add/remove syntax now matches other ircds more closely (#1074)
    • CS OP will regrant your channel AMODE, in case you removed it (#1516, #1307, thanks @jlu5!)
    • User passwords may no longer begin with : (#1571)
    • Improved documentation of CS AMODE and NS UNREGISTER (#1524, #1545, thanks @Mikaela!)
    • Disabling history disables history-related CAPs (#1549)

    Added

    • Implemented the new CHATHISTORY TARGETS API for listing direct message conversations (#1592, thanks @emersion, @hhirtz, @jwheare, @kylef!)
    • Implemented the new IRC-over-websockets draft, adding support for binary websockets and subprotocol negotiation (#1558, thanks @jwheare!)
    • Implemented the new bot mode spec (#1562)
    • Implemented the new forward mode spec (#1612, thanks @ProgVal!)
    • WARN NICK ACCOUNT_REQUIRED is sent on failed attempts to claim a reserved nickname (#1594)
    • NS CLIENTS LIST displays enabled client capabilities (#1576)
    • CS INFO with no arguments lists your registered channels (#765)
    • NS PASSWORD is now accepted as an alias for NS PASSWD (#1547)

    Internal

    • Upgraded to Go 1.16 (#1510)
    Source code(tar.gz)
    Source code(zip)
    oragono-2.6.0-rc1-checksums.txt(1.00 KB)
    oragono-2.6.0-rc1-freebsd-386.tar.gz(3.61 MB)
    oragono-2.6.0-rc1-freebsd-x86_64.tar.gz(3.81 MB)
    oragono-2.6.0-rc1-linux-386.tar.gz(3.62 MB)
    oragono-2.6.0-rc1-linux-arm64.tar.gz(3.49 MB)
    oragono-2.6.0-rc1-linux-armv6.tar.gz(3.59 MB)
    oragono-2.6.0-rc1-linux-armv7.tar.gz(3.59 MB)
    oragono-2.6.0-rc1-linux-x86_64.tar.gz(3.83 MB)
    oragono-2.6.0-rc1-macos-x86_64.tar.gz(3.92 MB)
    oragono-2.6.0-rc1-windows-386.zip(3.82 MB)
    oragono-2.6.0-rc1-windows-x86_64.zip(3.93 MB)
  • v2.5.0(Jan 31, 2021)

    We're pleased to announce Oragono 2.5.0, a new stable release.

    This release includes enhancements based on the needs of real-world operators, as well as bug fixes. Highlights include:

    • UBAN, a new "unified ban" system for server operators, with a corresponding CHANSERV HOWTOBAN command for channel operators (#1447)
    • A new forwarding/overflow channel mode +f (#1260)
    • Support for PROXY protocol v2 (#1389)

    This release includes changes to the config file format, including two breaking changes. One is fairly significant: enabling a websocket listener now requires the use of server.enforce-utf8, as has been the recommended default since 2.2.0 (so continuing to accept legacy non-UTF-8 content will require disabling websockets). The other is that the "unban" operator capability has been removed (it is now included in the "ban" capability). Other config changes are backwards compatible and do not require updating the file before upgrading.

    This release includes a database change. If you have datastore.autoupgrade set to true in your configuration, it will be automatically applied when you restart Oragono. Otherwise, you can update the database manually by running oragono upgradedb (see the manual for complete instructions).

    Many thanks to @jlu5, @kylef and @Mikaela for contributing patches, to @bogdomania, @eskimo, @happyhater, @jlu5, @kylef, @LukeHoersten, @Mikaela, @mogad0n, @robinlemon, and @vertisan for reporting issues and helping test, and to our translators for contributing translations.

    Config changes

    • Enabling websockets now requires server.enforce-utf8 = true (#1483)
    • proxy is now a top-level field of the listener config block; in particular, the PROXY protocol (v1 or v2) can now be required ahead of a plaintext connection. The field is still accepted in its legacy position (inside the tls block). (#1389, thanks @robinlemon!)
    • Added accounts.multiclient.always-on-expiration, allowing always-on clients to be timed out for inactivity (#810, thanks @bogdomania!)
    • local_ prefixes have been stripped from operator capability names, so that, e.g., local_ban is now just ban. The old names are still accepted. (#1442)
    • The local_unban operator capability has been removed (unbanning is now contained in the ban permission). (#1442)
    • The recommended value of accounts.bcrypt-cost is now 4, the minimum acceptable value (#1497)
    • server.ip-limits.custom-limits now accepts networks that contain multiple CIDRs; the old syntax is still accepted (#1421, thanks @Mikaela!
    • A new field, history.restrictions.query-cutoff, generalizes the old history.restrictions.enforce-registration-date (the old field is still accepted) (#1490, thanks @Mikaela!)
    • Added server.override-services-hostname, allowing the hostname of NickServ, ChanServ, etc. to be overridden (#1407, thanks @Mikaela!)
    • Added a boolean hide-sts key to the listener block; this can be used to hide the STS CAP when the listener is secured at layer 3 or 4 (e.g., by a VPN or an E2E mixnet). It will still be necessary to add the relevant IPs to secure-nets. (#1428, thanks @Mikaela!)

    Security

    • Improved validation of names and encodings for client-only tags (#1385)
    • Improved auditability of sensitive operator actions (#1443, thanks @mogad0n!)
    • DEFCON 4 and lower now require Tor users to authenticate with SASL (#1450)

    Fixed

    • Fixed NS UNSUSPEND requiring the casefolded / lowercase version of the account name (#1382, thanks @mogad0n!)
    • Fixed client-only tags in direct (user-to-user) PRIVMSG not being replayed (#1411)
    • Fixed many bugs in import of Anope and Atheme databases (#1403, #1423, #1424, #1431, #1435, #1439, #1444, thanks @jlu5, @kylef, and @Mikaela!)
    • Fixed case-handling bugs in RENAME (i.e., channel rename) (#1456, thanks @mogad0n!)
    • Fixed incorrect processing of color code escapes in MOTD files (#1467, thanks @mogad0n!)
    • STS is no longer advertised to Tor clients (#1428, thanks @Mikaela!)
    • Fixed HELP/HELPOP numerics not including the nick as an argument (#1472, thanks @kylef!)
    • Made connection registration snomasks less confusing (#1396, thanks @eskimo!)
    • Fixed duplicated nicks in KLINE response (#1379, thanks @mogad0n!)
    • The RELAYMSG tag name is now draft/relaymsg, conforming to the amended draft specification (#1468, thanks @jlu5!)
    • Fixed SAJOIN not sending a MODE line to the originating client (#1383, thanks @mogad0n!)
    • Improved consistency of message sources sent by CS AMODE (#1383, thanks @mogad0n!)
    • Fixed duplicated JOIN line sent to some clients using the draft/resume-0.5 extension (#1397, thanks @kylef!)
    • Added a warning that MySQL cannot be enabled by rehash (#1452, thanks @Mikaela!)

    Changed

    • Channel-user modes (e.g., +o, +v) of always-on clients are now persisted in the database (#1345)
    • /CHANSERV PURGE now takes ADD, DEL, and LIST subcommands; the separate UNPURGE command has been removed; PURGE ADD now requires a confirmation code (#1294, thanks @mogad0n!)
    • The characters <, >, ', ", and ; are no longer allowed in nicknames (previously registered account names containing these characters are still accepted) (#1436, thanks @happyhater!)
    • Authenticated clients from Tor now receive their (account-unique) always-on cloaked hostname; this allows channel operators to ban unauthenticated Tor users by banning *!*@tor-network.onion (#1479, thanks @mogad0n!)
    • Included the network name in the human-readable final parameter of 001 RPL_WELCOME (#1410)
    • RELAYMSG can now take client-only tags (#1470)
    • WebSocket listeners will attempt to negotiate the text.ircv3.net subprotocol; negotiating this is optional for clients (#1483)

    Added

    • Added UBAN, a new command giving server operators a unified interface to D-LINEs (IP bans), K-LINEs (NUH mask bans, which are now deprecated), and account suspensions (NS SUSPEND) (#1447)
    • Added CHANSERV HOWTOBAN, a ChanServ subcommand that helps channel operators choose an appropriate ban (#1447)
    • Added a new channel mode +f; users who cannot join the channel due to +i or +l will be forwarded to the channel specified by +f. (#1260)
    • Added support for the PROXY protocol v2 (#1389, thanks @robinlemon!)
    • Added support for /JOIN 0 (part all channels), requiring a confirmation code (#1417, thanks @Mikaela!)
    • Added support for grouped nicknames as SASL usernames (#1476, thanks @eskimo!)
    • Added history support for INVITE (#1409, thanks @Mikaela!)
    • Added a new channel setting accessible via /CS SET: history-cutoff, allowing the channel owner more fine-grained control over who can see history (#1490, thanks @Mikaela!)
    • Added the UTF8ONLY ISUPPORT token, allowing the server to advertise to clients that only UTF-8 content is accepted (#1483)
    • Added /NICKSERV RENAME, an operator-only command that can change the case of an account name (#1380, thanks @LukeHoersten!)

    Internal

    • Added caching for serialized messages (#1387)
    • Improved memory efficiency of line reading (#1231)
    Source code(tar.gz)
    Source code(zip)
    oragono-2.5.0-checksums.txt(990 bytes)
    oragono-2.5.0-freebsd-386.tar.gz(4.17 MB)
    oragono-2.5.0-freebsd-x86_64.tar.gz(4.41 MB)
    oragono-2.5.0-linux-386.tar.gz(4.18 MB)
    oragono-2.5.0-linux-arm64.tar.gz(4.06 MB)
    oragono-2.5.0-linux-armv6.tar.gz(4.13 MB)
    oragono-2.5.0-linux-armv7.tar.gz(4.12 MB)
    oragono-2.5.0-linux-x86_64.tar.gz(4.43 MB)
    oragono-2.5.0-macos-x86_64.tar.gz(4.58 MB)
    oragono-2.5.0-windows-386.zip(4.37 MB)
    oragono-2.5.0-windows-x86_64.zip(4.51 MB)
  • v2.5.0-rc1(Jan 24, 2021)

    We're pleased to be publishing the release candidate for 2.5.0 (the official release should follow in a week or so).

    This release includes enhancements based on the needs of real-world operators, as well as bug fixes. Highlights include:

    • UBAN, a new "unified ban" system for server operators, with a corresponding CHANSERV HOWTOBAN command for channel operators (#1447)
    • A new forwarding/overflow channel mode +f (#1260)
    • Support for PROXY protocol v2 (#1389)

    This release includes changes to the config file format, including two breaking changes. One is fairly significant: enabling a websocket listener now requires the use of server.enforce-utf8, as has been the recommended default since 2.2.0 (so continuing to accept legacy non-UTF-8 content will require disabling websockets). The other is that the "unban" operator capability has been removed (it is now included in the "ban" capability). Other config changes are backwards compatible and do not require updating the file before upgrading.

    This release includes a database change. If you have datastore.autoupgrade set to true in your configuration, it will be automatically applied when you restart Oragono. Otherwise, you can update the database manually by running oragono upgradedb (see the manual for complete instructions).

    Many thanks to @jlu5, @kylef and @Mikaela for contributing patches, to @bogdomania, @eskimo, @happyhater, @jlu5, @kylef, @LukeHoersten, @Mikaela, @mogad0n, @robinlemon, and @vertisan for reporting issues and helping test, and to our translators for contributing translations.

    Config changes

    • Enabling websockets now requires server.enforce-utf8 = true (#1483)
    • proxy is now a top-level field of the listener config block; in particular, the PROXY protocol (v1 or v2) can now be required ahead of a plaintext connection. The field is still accepted in its legacy position (inside the tls block). (#1389, thanks @robinlemon!)
    • Added accounts.multiclient.always-on-expiration, allowing always-on clients to be timed out for inactivity (#810, thanks @bogdomania!)
    • local_ prefixes have been stripped from operator capability names, so that, e.g., local_ban is now just ban. The old names are still accepted. (#1442)
    • The local_unban operator capability has been removed (unbanning is now contained in the ban permission). (#1442)
    • The recommended value of accounts.bcrypt-cost is now 4, the minimum acceptable value (#1497)
    • server.ip-limits.custom-limits now accepts networks that contain multiple CIDRs; the old syntax is still accepted (#1421, thanks @Mikaela!
    • A new field, history.restrictions.query-cutoff, generalizes the old history.restrictions.enforce-registration-date (the old field is still accepted) (#1490, thanks @Mikaela!)
    • Added server.override-services-hostname, allowing the hostname of NickServ, ChanServ, etc. to be overridden (#1407, thanks @Mikaela!)
    • Added a boolean hide-sts key to the listener block; this can be used to hide the STS CAP when the listener is secured at layer 3 or 4 (e.g., by a VPN or an E2E mixnet). It will still be necessary to add the relevant IPs to secure-nets. (#1428, thanks @Mikaela!)

    Security

    • Improved validation of names and encodings for client-only tags (#1385)
    • Improved auditability of sensitive operator actions (#1443, thanks @mogad0n!)
    • DEFCON 4 and lower now require Tor users to authenticate with SASL (#1450)

    Fixed

    • Fixed NS UNSUSPEND requiring the casefolded / lowercase version of the account name (#1382, thanks @mogad0n!)
    • Fixed client-only tags in direct (user-to-user) PRIVMSG not being replayed (#1411)
    • Fixed many bugs in import of Anope and Atheme databases (#1403, #1423, #1424, #1431, #1435, #1439, #1444, thanks @jlu5, @kylef, and @Mikaela!)
    • Fixed case-handling bugs in RENAME (i.e., channel rename) (#1456, thanks @mogad0n!)
    • Fixed incorrect processing of color code escapes in MOTD files (#1467, thanks @mogad0n!)
    • STS is no longer advertised to Tor clients (#1428, thanks @Mikaela!)
    • Fixed HELP/HELPOP numerics not including the nick as an argument (#1472, thanks @kylef!)
    • Made connection registration snomasks less confusing (#1396, thanks @eskimo!)
    • Fixed duplicated nicks in KLINE response (#1379, thanks @mogad0n!)
    • The RELAYMSG tag name is now draft/relaymsg, conforming to the amended draft specification (#1468, thanks @jlu5!)
    • Fixed SAJOIN not sending a MODE line to the originating client (#1383, thanks @mogad0n!)
    • Improved consistency of message sources sent by CS AMODE (#1383, thanks @mogad0n!)
    • Fixed duplicated JOIN line sent to some clients using the draft/resume-0.5 extension (#1397, thanks @kylef!)
    • Added a warning that MySQL cannot be enabled by rehash (#1452, thanks @Mikaela!)

    Changed

    • Channel-user modes (e.g., +o, +v) of always-on clients are now persisted in the database (#1345)
    • /CHANSERV PURGE now takes ADD, DEL, and LIST subcommands; the separate UNPURGE command has been removed; PURGE ADD now requires a confirmation code (#1294, thanks @mogad0n!)
    • The characters <, >, ', ", and ; are no longer allowed in nicknames (previously registered account names containing these characters are still accepted) (#1436, thanks @happyhater!)
    • Authenticated clients from Tor now receive their (account-unique) always-on cloaked hostname; this allows channel operators to ban unauthenticated Tor users by banning *!*@tor-network.onion (#1479, thanks @mogad0n!)
    • Included the network name in the human-readable final parameter of 001 RPL_WELCOME (#1410)
    • RELAYMSG can now take client-only tags (#1470)
    • WebSocket listeners will attempt to negotiate the text.ircv3.net subprotocol; negotiating this is optional for clients (#1483)

    Added

    • Added UBAN, a new command giving server operators a unified interface to D-LINEs (IP bans), K-LINEs (NUH mask bans, which are now deprecated), and account suspensions (NS SUSPEND) (#1447)
    • Added CHANSERV HOWTOBAN, a ChanServ subcommand that helps channel operators choose an appropriate ban (#1447)
    • Added a new channel mode +f; users who cannot join the channel due to +i or +l will be forwarded to the channel specified by +f. (#1260)
    • Added support for the PROXY protocol v2 (#1389, thanks @robinlemon!)
    • Added support for /JOIN 0 (part all channels), requiring a confirmation code (#1417, thanks @Mikaela!)
    • Added support for grouped nicknames as SASL usernames (#1476, thanks @eskimo!)
    • Added history support for INVITE (#1409, thanks @Mikaela!)
    • Added a new channel setting accessible via /CS SET: history-cutoff, allowing the channel owner more fine-grained control over who can see history (#1490, thanks @Mikaela!)
    • Added the UTF8ONLY ISUPPORT token, allowing the server to advertise to clients that only UTF-8 content is accepted (#1483)
    • Added /NICKSERV RENAME, an operator-only command that can change the case of an account name (#1380, thanks @LukeHoersten!)

    Internal

    • Added caching for serialized messages (#1387)
    • Improved memory efficiency of line reading (#1231)
    Source code(tar.gz)
    Source code(zip)
    oragono-2.5.0-rc1-checksums.txt(1.00 KB)
    oragono-2.5.0-rc1-freebsd-386.tar.gz(4.17 MB)
    oragono-2.5.0-rc1-freebsd-x86_64.tar.gz(4.41 MB)
    oragono-2.5.0-rc1-linux-386.tar.gz(4.18 MB)
    oragono-2.5.0-rc1-linux-arm64.tar.gz(4.05 MB)
    oragono-2.5.0-rc1-linux-armv6.tar.gz(4.13 MB)
    oragono-2.5.0-rc1-linux-armv7.tar.gz(4.12 MB)
    oragono-2.5.0-rc1-linux-x86_64.tar.gz(4.43 MB)
    oragono-2.5.0-rc1-macos-x86_64.tar.gz(4.58 MB)
    oragono-2.5.0-rc1-windows-386.zip(4.36 MB)
    oragono-2.5.0-rc1-windows-x86_64.zip(4.50 MB)
  • v2.4.0(Nov 8, 2020)

    We're pleased to announce Oragono 2.4.0, a new stable release.

    This release includes a number of exciting enhancements and fixes. Here are some highlights:

    • Support for migrating an Anope or Atheme database to Oragono (#1042)
    • A pluggable system for validating external IPs, e.g., via DNSBLs (#68, thanks @moortens!)
    • draft/relaymsg, a new draft extension simplifying bridging with other chat systems (thanks @jlu5!)
    • New moderation tools: +u ("auditorium", #1300), +U ("op-moderated", #1178), +M ("moderated-registered", #1182, thanks @ajaspers!), and +b m: (an extban for muting users, #307)

    This release includes changes to the config file format, including one breaking change: roleplay.enabled now defaults to false (the new recommended default) instead of true when unset. Other config changes are backwards compatible and do not require updating the file before upgrading.

    This release includes a database change. If you have datastore.autoupgrade set to true in your configuration, it will be automatically applied when you restart Oragono. Otherwise, you can update the database manually by running oragono upgradedb (see the manual for complete instructions).

    Many thanks to @ajaspers, @jesopo, @moortens, and @RunBarryRun for contributing patches, to @csmith for contributing code reviews, to @ajaspers, @Amiga60077, @bogdomania, @csmith, @edk0, @eskimo, @jlu5, @jwheare, @KoraggKnightWolf, @Mitaka8, @mogad0n, @RyanSquared, and @vertisan for reporting issues and helping test, and to our translators for contributing translations.

    Config changes

    • Added server.ip-cloaking.enabled-for-always-on, which generates a unique hostname for each always-on client. The recommended default value of this field is true (#1312)
    • Added server.coerce-ident; if this is set to a string value, all user/ident fields supplied by clients are ignored and replaced with this value. The recommended default value of this field is ~u. This simplifies bans. (#1340)
    • Simplified the config file format for email verification into a new accounts.nick-reservation.email-verification section. The old format (callbacks) is still accepted (#1075)
    • The recommended value of roleplay.enabled is now false; this field now defaults to false when unset (#1240, #1271)
    • Added server.relaymsg section for configuring the new draft/relaymsg capability; added the new relaymsg operator capability for exercising it (#1119)
    • Added allow-environment-overrides config variable, allowing config options to be overridden by environment variables. See the manual for more details. (#1049, thanks @csmith!)
    • Added server.ip-check-script for configuring IP check plugins (#68, #1267, thanks @moortens!)
    • Added max-concurrency restriction to accounts.auth-script section. The recommended default value is 64 (0 or unset disable the restriction) (#1267)
    • Added accounts.registration.allow-before-connect; this allows the use of the new REGISTER command before connecting to the server (#1075)
    • Added hidden option in operator blocks: if set to true, operator status is hidden from commands like WHOIS that would otherwise display it (#1194)
    • Added accounts.nick-reservation.forbid-anonymous-nick-changes, which forbids anonymous users from changing their nicknames after initially connecting (#1337, thanks @Amiga60077!)
    • Added channels.invite-expiration, allowing invites to +i channels to expire after a given amount of time (#1171)

    Security

    • Added /NICKSERV CLIENTS LOGOUT command for disconnecting clients connected to a user account (#1072, #1272, thanks @ajaspers!)
    • Disallowed the use of service nicknames during roleplaying (#1240, thanks @Mitaka8!)
    • Improved security properties of INVITE for invite-only channels, including an UNINVITE command (#1171)

    Removed

    • Removed the request queue system for HostServ, i.e., the REQUEST, APPROVE, and REJECT subcommands of HOSTSERV (#1346)

    Fixed

    • PONG is now sent with the server name as the first parameter, matching the behavior of other ircds (#1249, thanks @jesopo!)
    • It was not possible to set or unset the +T no-CTCP user mode; this has been fixed (#1299, thanks @mogad0n!)
    • Fixed edge cases with /NICKSERV SAREGISTER of confusable nicknames (#1322, thanks @mogad0n!)
    • Fixed websocket listeners with proxy-before-TLS enabled closing on invalid PROXY lines (#1269, thanks @RyanSquared!)
    • Fixed error responses and history for SANICK (#1277, #1278, thanks @eskimo!)
    • Ensured that stored realnames of always-on clients are deleted during account unregistration (#1330)
    • Whitespace is now stripped from KLINEs (#1327, thanks @mogad0n!)
    • Fixed incorrect LUSERS counts caused by KLINE (#1303, thanks @mogad0n!)
    • CHATHISTORY queries for invalid channels now get an empty batch instead of a FAIL (#1322)
    • fakelag.messages-per-window = 0 no longer causes a panic (#861, thanks @vertisan!)

    Added

    • Added oragono importdb command for importing a converted Anope or Atheme database; see the manual for details (#1042)
    • Added support for the new draft/relaymsg extension, which simplifies bridging IRC with other protocols relaymsg (#1119, thanks @jlu5!)
    • Added ip-check-script, a scripting API for restricting access by client IP. We provide oragono-dnsbl, an external script that can query DNSBLs for this purpose (#68, #1267, thanks @moortens!)
    • Added channel mode +u. This is an "auditorium" mode that prevents unprivileged users from seeing each other's JOIN and PART lines. It's useful for large public-announcement channels, possibly in conjunction with +m (#1300)
    • Added channel mode +U. This is an "op-moderated" mode; messages from unprivileged users are sent only to channel operators, who can then choose to grant them +v. (#1178)
    • Added a mute extban +b m:: users matching the ban expression (e.g., +b m:*!*@j6dwi4vacx47y.irc) will be able to join the channel, but will be unable to speak. (#307)
    • Added support for the new draft/register extension, which exposes a cleaner account registration API to clients (#1075, thanks @edk0!)
    • Added a 379 RPL_WHOISMODES line to the WHOIS response, making it easier for operators to see other users' modes (#769, thanks @Amiga60077 and @KoraggKnightWolf!)
    • Added /CHANSERV DEOP command for removing channel operator privileges (#361, thanks @RunBarryRun!)
    • Added r flag to /WHO responses for registered nicknames (#1366, thanks @Amiga60077!)

    Changed

    • Always-on clients now receive a user/ident of ~u by default, instead of ~user; this can be changed by setting the coerce-ident field (#1340)
    • /NICKSERV SUSPEND has been modified to take subcommands (ADD, DEL, and LIST); the ADD subcommand now accepts time duration and reason arguments. See /msg NickServ HELP SUSPEND for details. (#1274, thanks @mogad0n!)
    • Only the channel founder can kick the channel founder, regardless of either party's modes (#1262)
    • /NICKSERV SESSIONS is now /NICKSERV CLIENTS LIST, but the old command is still accepted (#1272, thanks @ajaspers!)
    • Improved SETNAME behavior for legacy clients (#1358, thanks @KoraggKnightWolf!)
    • Halfops can set the channel topic (#1306)
    • Full client certificates are now passed to auth scripts. This allows for more flexible checks on certificates, including verification against an internal CA (#414)

    Internal

    • Added a logline for debugging client disconnections (#1293)
    • Renamed conventional.yaml to traditional.yaml (#1350)
    • Integration tests are now run during CI (#1279)
    Source code(tar.gz)
    Source code(zip)
    oragono-2.4.0-checksums.txt(990 bytes)
    oragono-2.4.0-freebsd-386.tar.gz(4.12 MB)
    oragono-2.4.0-freebsd-x86_64.tar.gz(4.36 MB)
    oragono-2.4.0-linux-386.tar.gz(4.13 MB)
    oragono-2.4.0-linux-arm64.tar.gz(4.01 MB)
    oragono-2.4.0-linux-armv6.tar.gz(4.08 MB)
    oragono-2.4.0-linux-armv7.tar.gz(4.08 MB)
    oragono-2.4.0-linux-x86_64.tar.gz(4.38 MB)
    oragono-2.4.0-macos-x86_64.tar.gz(4.53 MB)
    oragono-2.4.0-windows-386.zip(4.31 MB)
    oragono-2.4.0-windows-x86_64.zip(4.45 MB)
  • v2.4.0-rc1(Nov 1, 2020)

    We're pleased to be publishing the release candidate for 2.4.0 (the official release should follow in a week or so).

    This release includes a number of exciting enhancements and fixes. Here are some highlights:

    • Support for migrating an Anope or Atheme database to Oragono (#1042)
    • A pluggable system for validating external IPs, e.g., via DNSBLs (#68, thanks @moortens!)
    • draft/relaymsg, a new draft extension simplifying bridging with other chat systems (thanks @jlu5!)
    • New moderation tools: +u ("auditorium", #1300), +U ("op-moderated", #1178), +M ("moderated-registered", #1182, thanks @ajaspers!), and +b m: (an extban for muting users, #307)

    This release includes changes to the config file format, including one breaking change: roleplay.enabled now defaults to false (the new recommended default) instead of true when unset. Other config changes are backwards compatible and do not require updating the file before upgrading.

    This release includes a database change. If you have datastore.autoupgrade set to true in your configuration, it will be automatically applied when you restart Oragono. Otherwise, you can update the database manually by running oragono upgradedb (see the manual for complete instructions).

    Many thanks to @ajaspers, @jesopo, @moortens, and @RunBarryRun for contributing patches, to @csmith for contributing code reviews, to @ajaspers, @Amiga60077, @bogdomania, @csmith, @edk0, @eskimo, @jlu5, @jwheare, @KoraggKnightWolf, @Mitaka8, @mogad0n, @RyanSquared, and @vertisan for reporting issues and helping test, and to our translators for contributing translations.

    Config changes

    • Added server.ip-cloaking.enabled-for-always-on, which generates a unique hostname for each always-on client. The recommended default value of this field is true (#1312)
    • Added server.coerce-ident; if this is set to a string value, all user/ident fields supplied by clients are ignored and replaced with this value. The recommended default value of this field is ~u. This simplifies bans. (#1340)
    • Simplified the config file format for email verification into a new accounts.nick-reservation.email-verification section. The old format (callbacks) is still accepted (#1075)
    • The recommended value of roleplay.enabled is now false; this field now defaults to false when unset (#1240, #1271)
    • Added server.relaymsg section for configuring the new draft/relaymsg capability; added the new relaymsg operator capability for exercising it (#1119)
    • Added allow-environment-overrides config variable, allowing config options to be overridden by environment variables. See the manual for more details. (#1049, thanks @csmith!)
    • Added server.ip-check-script for configuring IP check plugins (#68, #1267, thanks @moortens!)
    • Added max-concurrency restriction to accounts.auth-script section. The recommended default value is 64 (0 or unset disable the restriction) (#1267)
    • Added accounts.registration.allow-before-connect; this allows the use of the new REGISTER command before connecting to the server (#1075)
    • Added hidden option in operator blocks: if set to true, operator status is hidden from commands like WHOIS that would otherwise display it (#1194)
    • Added accounts.nick-reservation.forbid-anonymous-nick-changes, which forbids anonymous users from changing their nicknames after initially connecting (#1337, thanks @Amiga60077!)
    • Added channels.invite-expiration, allowing invites to +i channels to expire after a given amount of time (#1171)

    Security

    • Added /NICKSERV CLIENTS LOGOUT command for disconnecting clients connected to a user account (#1072, #1272, thanks @ajaspers!)
    • Disallowed the use of service nicknames during roleplaying (#1240, thanks @Mitaka8!)
    • Improved security properties of INVITE for invite-only channels, including an UNINVITE command (#1171)

    Removed

    • Removed the request queue system for HostServ, i.e., the REQUEST, APPROVE, and REJECT subcommands of HOSTSERV (#1346)

    Fixed

    • PONG is now sent with the server name as the first parameter, matching the behavior of other ircds (#1249, thanks @jesopo!)
    • It was not possible to set or unset the +T no-CTCP user mode; this has been fixed (#1299, thanks @mogad0n!)
    • Fixed edge cases with /NICKSERV SAREGISTER of confusable nicknames (#1322, thanks @mogad0n!)
    • Fixed websocket listeners with proxy-before-TLS enabled closing on invalid PROXY lines (#1269, thanks @RyanSquared!)
    • Fixed error responses and history for SANICK (#1277, #1278, thanks @eskimo!)
    • Ensured that stored realnames of always-on clients are deleted during account unregistration (#1330)
    • Whitespace is now stripped from KLINEs (#1327, thanks @mogad0n!)
    • Fixed incorrect LUSERS counts caused by KLINE (#1303, thanks @mogad0n!)
    • CHATHISTORY queries for invalid channels now get an empty batch instead of a FAIL (#1322)
    • fakelag.messages-per-window = 0 no longer causes a panic (#861, thanks @vertisan!)

    Added

    • Added oragono importdb command for importing a converted Anope or Atheme database; see the manual for details (#1042)
    • Added support for the new draft/relaymsg extension, which simplifies bridging IRC with other protocols relaymsg (#1119, thanks @jlu5!)
    • Added ip-check-script, a scripting API for restricting access by client IP. We provide oragono-dnsbl, an external script that can query DNSBLs for this purpose (#68, #1267, thanks @moortens!)
    • Added channel mode +u. This is an "auditorium" mode that prevents unprivileged users from seeing each other's JOIN and PART lines. It's useful for large public-announcement channels, possibly in conjunction with +m (#1300)
    • Added channel mode +U. This is an "op-moderated" mode; messages from unprivileged users are sent only to channel operators, who can then choose to grant them +v. (#1178)
    • Added a mute extban +b m:: users matching the ban expression (e.g., +b m:*!*@j6dwi4vacx47y.irc) will be able to join the channel, but will be unable to speak. (#307)
    • Added support for the new draft/register extension, which exposes a cleaner account registration API to clients (#1075, thanks @edk0!)
    • Added a 379 RPL_WHOISMODES line to the WHOIS response, making it easier for operators to see other users' modes (#769, thanks @Amiga60077 and @KoraggKnightWolf!)
    • Added /CHANSERV DEOP command for removing channel operator privileges (#361, thanks @RunBarryRun!)
    • Added r flag to /WHO responses for registered nicknames (#1366, thanks @Amiga60077!)

    Changed

    • Always-on clients now receive a user/ident of ~u by default, instead of ~user; this can be changed by setting the coerce-ident field (#1340)
    • /NICKSERV SUSPEND has been modified to take subcommands (ADD, DEL, and LIST); the ADD subcommand now accepts time duration and reason arguments. See /msg NickServ HELP SUSPEND for details. (#1274, thanks @mogad0n!)
    • Only the channel founder can kick the channel founder, regardless of either party's modes (#1262)
    • /NICKSERV SESSIONS is now /NICKSERV CLIENTS LIST, but the old command is still accepted (#1272, thanks @ajaspers!)
    • Improved SETNAME behavior for legacy clients (#1358, thanks @KoraggKnightWolf!)
    • Halfops can set the channel topic (#1306)
    • Full client certificates are now passed to auth scripts. This allows for more flexible checks on certificates, including verification against an internal CA (#414)

    Internal

    • Added a logline for debugging client disconnections (#1293)
    • Renamed conventional.yaml to traditional.yaml (#1350)
    • Integration tests are now run during CI (#1279)
    Source code(tar.gz)
    Source code(zip)
    oragono-2.4.0-rc1-checksums.txt(1.00 KB)
    oragono-2.4.0-rc1-freebsd-386.tar.gz(4.12 MB)
    oragono-2.4.0-rc1-freebsd-x86_64.tar.gz(4.36 MB)
    oragono-2.4.0-rc1-linux-386.tar.gz(4.12 MB)
    oragono-2.4.0-rc1-linux-arm64.tar.gz(4.00 MB)
    oragono-2.4.0-rc1-linux-armv6.tar.gz(4.08 MB)
    oragono-2.4.0-rc1-linux-armv7.tar.gz(4.07 MB)
    oragono-2.4.0-rc1-linux-x86_64.tar.gz(4.37 MB)
    oragono-2.4.0-rc1-macos-x86_64.tar.gz(4.52 MB)
    oragono-2.4.0-rc1-windows-386.zip(4.31 MB)
    oragono-2.4.0-rc1-windows-x86_64.zip(4.45 MB)
  • v2.3.0(Sep 6, 2020)

    We're pleased to announce Oragono 2.3.0, a new stable release.

    This release contains primarily bug fixes, but includes one notable feature enhancement: a change contributed by @hhirtz that updates the draft/rename specification to correspond to the new (soon-to-be) published draft.

    Many thanks to @hhirtz for contributing patches, to @bogdomania, @digitalcircuit, @ivan-avalos, @jesopo, @kylef, @Mitaka8, @mogad0n, and @ProgVal for reporting issues and helping test, and to our translators for contributing translations.

    This release includes no changes to the config file format or database changes.

    Config changes

    • The recommended value of lookup-hostnames for configurations that cloak IPs (as has been the default since 2.1.0) is now false (#1228)

    Security

    • Mitigated a potential DoS attack on websocket listeners (#1226)

    Removed

    • Removed /HOSTSERV OFFERLIST and related commands; this functionality is superseded by IP cloaking (#1190)

    Fixed

    • Fixed an edge case in handling no-op nick changes (#1242)
    • Fixed edge cases with users transitioning in and out of always-on status (#1218, #1219, thanks @bogdomania!)
    • Fixed a race condition related to the registration timeout (#1225, thanks @hhirtz!)
    • Fixed incorrectly formatted account tags on some messages (#1254, thanks @digitalcircuit!)
    • Improved checks for invalid config files (#1244, thanks @ivan-avalos!)
    • Fixed messages to services and *playback not receiving echo-message when applicable (#1204, thanks @kylef!)
    • Fixed a help string (#1237, thanks @Mitaka8!)

    Changed

    • Updated draft/rename implementation to the latest draft (#1223, thanks @hhirtz!)

    Internal

    • Official release builds now use Go 1.15 (#1195)
    • /INFO now includes the Go version (#1234)
    Source code(tar.gz)
    Source code(zip)
    oragono-2.3.0-checksums.txt(990 bytes)
    oragono-2.3.0-freebsd-386.tar.gz(4.42 MB)
    oragono-2.3.0-freebsd-x86_64.tar.gz(4.66 MB)
    oragono-2.3.0-linux-386.tar.gz(4.43 MB)
    oragono-2.3.0-linux-arm64.tar.gz(4.31 MB)
    oragono-2.3.0-linux-armv6.tar.gz(4.38 MB)
    oragono-2.3.0-linux-armv7.tar.gz(4.38 MB)
    oragono-2.3.0-linux-x86_64.tar.gz(4.68 MB)
    oragono-2.3.0-macos-x86_64.tar.gz(4.82 MB)
    oragono-2.3.0-windows-386.zip(4.67 MB)
    oragono-2.3.0-windows-x86_64.zip(4.80 MB)
  • v2.3.0-rc2(Aug 30, 2020)

  • v2.3.0-rc1(Aug 23, 2020)

    We're pleased to be publishing the release candidate for 2.3.0 (the official release should follow in a week or so).

    This release contains primarily bug fixes, but includes one notable feature enhancement: a change contributed by @hhirtz that updates the draft/rename specification to correspond to the new (soon-to-be) published draft.

    Many thanks to @hhirtz for contributing patches, to @bogdomania, @jesopo, @kylef, @Mitaka8,and @mogad0n for reporting issues and helping test, and to our translators for contributing translations.

    This release includes no changes to the config file format or database changes.

    Config changes

    • The recommended value of lookup-hostnames for configurations that cloak IPs (as has been the default since 2.1.0) is now false (#1228)

    Security

    • Mitigated a potential DoS attack on websocket listeners (#1226)

    Removed

    • Removed /HOSTSERV OFFERLIST and related commands; this functionality is superseded by IP cloaking (#1190)

    Fixed

    • Fixed an edge case in handling no-op nick changes (#1242)
    • Fixed edge cases with users transitioning in and out of always-on status (#1218, #1219, thanks @bogdomania!)
    • Fixed a race condition related to the registration timeout (#1225, thanks @hhirtz!)
    • Fixed messages to services and *playback not receiving echo-message when applicable (#1204, thanks @kylef!)
    • Fixed a help string (#1237, thanks @Mitaka8!)

    Changed

    • Updated draft/rename implementation to the latest draft (#1223, thanks @hhirtz!)

    Internal

    • Official release builds now use Go 1.15 (#1195)
    • /INFO now includes the Go version (#1234)
    Source code(tar.gz)
    Source code(zip)
    oragono-2.3.0-rc1-checksums.txt(1.00 KB)
    oragono-2.3.0-rc1-freebsd-386.tar.gz(4.42 MB)
    oragono-2.3.0-rc1-freebsd-x86_64.tar.gz(4.66 MB)
    oragono-2.3.0-rc1-linux-386.tar.gz(4.43 MB)
    oragono-2.3.0-rc1-linux-arm64.tar.gz(4.31 MB)
    oragono-2.3.0-rc1-linux-armv6.tar.gz(4.38 MB)
    oragono-2.3.0-rc1-linux-armv7.tar.gz(4.38 MB)
    oragono-2.3.0-rc1-linux-x86_64.tar.gz(4.68 MB)
    oragono-2.3.0-rc1-macos-x86_64.tar.gz(4.82 MB)
    oragono-2.3.0-rc1-windows-386.zip(4.67 MB)
    oragono-2.3.0-rc1-windows-x86_64.zip(4.80 MB)
  • v2.2.0(Jul 26, 2020)

    We're pleased to announce Oragono 2.2.0, a new stable release.

    This release contains several notable enhancements, as well as bug fixes:

    • Support for tracking seen/missed messages across multiple devices (#843)
    • WHOX support contributed by @jesopo (#938)
    • Authentication of users via external scripts (#1107)

    Many thanks to @clukawski and @jesopo for contributing patches, to @ajaspers, @bogdomania, @csmith, @daurnimator, @emersonveenstra, @eskil, @eskimo, Geo-, @happyhater, @jesopo, @jwheare, @k4bek4be, @KoraggKnightWolf, @kylef, @LukeHoersten, @mogad0n, r3m, @RyanSquared, savoyard, and @wrmsr for reporting issues and helping test, and to our translators for contributing translations.

    This release includes changes to the config file format, including one breaking change: timeout is no longer an acceptable value of accounts.nick-reservation.method. (If you were using it, we suggest strict as a replacement.) All other changes to the config file format are backwards compatible and do not require updating before restart.

    This release includes a database change. If you have datastore.autoupgrade set to true in your configuration, it will be automatically applied when you restart Oragono. Otherwise, you can update the database manually by running oragono upgradedb (see the manual for complete instructions).

    Removed

    • Timeout-based nickname enforcement has been removed. We recommend strict as the default enforcement method. Users who configured timeout for their account will be upgraded to strict. With accounts.login-via-pass-command enabled, clients lacking support for SASL can authenticate via the PASS (server password command) by sending account_name:account_password as the server password. (#1027)
    • Native support for LDAP has been removed. LDAP is now supported via the external oragono-ldap plugin; see its repository page for details. (#1142, #1107)

    Config changes

    • Added server.enforce-utf8, controlling whether the server enforces that messages be valid UTF-8; a value of true for this is now the recommended default (#1151)
    • Added history.tagmsg-storage for configuring which TAGMSG are stored in history; if this is not configured, TAGMSG will not be stored (#1172)
    • All TLS certificate fingerprints in the config file are now named certfp instead of fingerprint (the old name of fingerprint is still accepted) (#1050, thanks @RyanSquared!)
    • Added accounts.auth-script section for configuring external authentication scripts (#1107, thanks @daurnimator!)
    • Removed accounts.ldap section for configuring LDAP; LDAP is now available via the auth-script plugin interface (#1142)
    • Added defcon operator capability, allowing use of the new /DEFCON command (#328)
    • Default awaylen, kicklen, and topiclen limits now reflect the 512-character line limit (#1112, thanks @k4bek4be!)
    • Added extjwt section for configuring the EXTJWT extension (#948, #1136)
    • login-via-pass-command: true is now a recommended default (#1186)

    Added

    • Added support for WHOX, contributed by @jesopo (#938, thanks!)
    • Added support for tracking missed messages across multiple devices; see the "history" section of the manual for details (#843, thanks @jwheare and @wrmsr!)
    • Added /NICKSERV SUSPEND and /NICKSERV UNSUSPEND commands, allowing operators to suspend access to an abusive user account (#1135)
    • Added support for external authentication systems, via subprocess ("auth-script") invocation (#1107, thanks @daurnimator!)
    • Added the /DEFCON command, allowing operators to respond to spam or DoS attacks by disabling features at runtime without a rehash. (This feature requires that the operator have a newly defined capability, named defcon; this can be added to the appropriate oper blocks in the config file.) (#328, thanks @bogdomania!)
    • Added support for the EXTJWT draft extension, allowing Oragono to be integrated with other systems like Jitsi (#948, #1136)
    • Services (NickServ, ChanServ, etc.) now respond to CTCP VERSION messages (#1055, thanks @jesopo!)
    • Added BOT ISUPPORT token, plus a B flag for bots in 352 RPL_WHOREPLY (#1117)
    • Added support for the +T no-CTCP user mode (#1007, thanks @clukawski!)
    • Added support for persisting the realname of always-on clients (#1065, thanks @clukawski!)
    • Added a warning on incorrect arguments to /NICKSERV REGISTER (#1179, thanks @LukeHoersten!)
    • /NICKSERV SET PASSWORD now sends a warning (#1208)

    Fixed

    • Fixed channels with only invisible users not being displayed in /LIST output (#1161, thanks @bogdomania!)
    • Fixed INVITE not overriding a +b ban (#1168)
    • Fixed incorrect CHGHOST lines during authentication with /NICKSERV IDENTIFY under some circumstances (#1108, thanks Geo-!)
    • Fixed incorrect CHGHOST lines sent to users during connection registration (#1125, thanks @jesopo!)
    • Fixed a number of issues affecting the znc.in/playback capability, in particular restoring compatibility with Palaver (#1205, thanks @kylef!)
    • Fixed interaction of auto-away with the regular /AWAY command (#1207)
    • Fixed an incorrect interaction between always-on and /NS SAREGISTER (#1216)
    • Fixed a race condition where nicknames of signed-out users could remain in the channel names list (#1166, thanks @eskimo!)
    • Fixed the last line of the MOTD being truncated in the absence of a terminating \n (#1167, thanks @eskimo!)
    • Fixed away-notify lines not being sent on channel JOIN (#1198, thanks savoyard!)
    • Fixed incorrect source of some nickserv messages (#1185)
    • Fixed idle time being updated on non-PRIVMSG commands (thanks r3m and @happyhater!)
    • Fixed /NICKSERV UNREGISTER and /NICKSERV ERASE not deleting stored user modes (#1157)

    Security

    • Connections to an STS-only listener no longer reveal the exact server version or server creation time (#802, thanks @csmith!)

    Changed

    • /DLINE now operates on individual client connections (#1135)
    • When using the multiclient feature, each client now has its own independent MONITOR list (#1053, thanks @ajaspers!)
    • MONITOR L now lists the nicknames in the form they were originally sent with MONITOR +, without casefolding (#1083)
    • We now send the traditional 445 ERR_SUMMONDISABLED and 446 ERR_USERSDISABLED in response to the SUMMON and USERS commands (#1078, thanks @KoraggKnightWolf!)
    • RPL_ISUPPORT parameters with no values are now sent without an = (#1067, #1069, #1091, thanks @KoraggKnightWolf and @jesopo!)
    • TAGMSG storage is now controlled via the history.tagmsg-storage config block (#1172)
    • /NICKSERV CERT ADD with no argument now adds the user's current TLS certificate fingerprint, when applicable (#1059, thanks @emersonveenstra!)

    Internal

    • The config file containing recommended defaults is now named default.yaml, instead of oragono.yaml (#1130, thanks @k4bek4be!)
    • The output of the /INFO command now includes the full git hash, when applicable (#1105)
    Source code(tar.gz)
    Source code(zip)
    oragono-2.2.0-checksums.txt(990 bytes)
    oragono-2.2.0-freebsd-386.tar.gz(5.02 MB)
    oragono-2.2.0-freebsd-x86_64.tar.gz(5.20 MB)
    oragono-2.2.0-linux-386.tar.gz(5.02 MB)
    oragono-2.2.0-linux-arm64.tar.gz(4.85 MB)
    oragono-2.2.0-linux-armv6.tar.gz(4.93 MB)
    oragono-2.2.0-linux-armv7.tar.gz(4.92 MB)
    oragono-2.2.0-linux-x86_64.tar.gz(5.22 MB)
    oragono-2.2.0-macos-x86_64.tar.gz(5.37 MB)
    oragono-2.2.0-windows-386.zip(5.10 MB)
    oragono-2.2.0-windows-x86_64.zip(5.28 MB)
  • v2.2.0-rc1(Jul 19, 2020)

    We're pleased to be publishing the release candidate for 2.2.0 (the official release should follow in a week or so).

    This release contains several notable enhancements, as well as bug fixes:

    • Support for tracking seen/missed messages across multiple devices (#843)
    • WHOX support contributed by @jesopo (#938)
    • Authentication of users via external scripts (#1107)

    Many thanks to @clukawski and @jesopo for contributing patches, to @ajaspers, @bogdomania, @csmith, @daurnimator, @emersonveenstra, @eskimo, Geo-, @happyhater, @jesopo, @jwheare, @k4bek4be, @KoraggKnightWolf, @LukeHoersten, @mogad0n, r3m, @RyanSquared, and savoyard for reporting issues and helping test, and to our translators for contributing translations.

    This release includes changes to the config file format, including one breaking change: timeout is no longer an acceptable value of accounts.nick-reservation.method. (If you were using it, we suggest strict as a replacement.) All other changes to the config file format are backwards compatible and do not require updating before restart.

    This release includes a database change. If you have datastore.autoupgrade set to true in your configuration, it will be automatically applied when you restart Oragono. Otherwise, you can update the database manually by running oragono upgradedb (see the manual for complete instructions).

    Removed

    • Timeout-based nickname enforcement has been removed. We recommend strict as the default enforcement method. Users who configured timeout for their account will be upgraded to strict. With accounts.login-via-pass-command enabled, clients lacking support for SASL can authenticate via the PASS (server password command) by sending account_name:account_password as the server password. (#1027)
    • Native support for LDAP has been removed. LDAP is now supported via the external oragono-ldap plugin; see its repository page for details. (#1142, #1107)

    Config changes

    • Added server.enforce-utf8, controlling whether the server enforces that messages be valid UTF-8; a value of true for this is now the recommended default (#1151)
    • Added history.tagmsg-storage for configuring which TAGMSG are stored in history; if this is not configured, TAGMSG will not be stored (#1172)
    • All TLS certificate fingerprints in the config file are now named certfp instead of fingerprint (the old name of fingerprint is still accepted) (#1050, thanks @RyanSquared!)
    • Added accounts.auth-script section for configuring external authentication scripts (#1107, thanks @daurnimator!)
    • Removed accounts.ldap section for configuring LDAP; LDAP is now available via the auth-script plugin interface (#1142)
    • Added defcon operator capability, allowing use of the new /DEFCON command (#328)
    • Default awaylen, kicklen, and topiclen limits now reflect the 512-character line limit (#1112, thanks @k4bek4be!)
    • Added extjwt section for configuring the EXTJWT extension (#948, #1136)
    • login-via-pass-command: true is now a recommended default (#1186)

    Added

    • Added support for WHOX, contributed by @jesopo (thanks!)
    • Added support for tracking missed messages across multiple devices; see the "history" section of the manual for details (#843, thanks @jwheare and @wrmsr!)
    • Added /NICKSERV SUSPEND and /NICKSERV UNSUSPEND commands, allowing operators to suspend access to an abusive user account (#1135)
    • Added support for external authentication systems, via subprocess ("auth-script") invocation (#1107, thanks @daurnimator!)
    • Added the /DEFCON command, allowing operators to respond to spam or DoS attacks by disabling features at runtime without a rehash. (This feature requires that the operator have a newly defined capability, named defcon; this can be added to the appropriate oper blocks in the config file.) (#328, thanks @bogdomania!)
    • Added support for the EXTJWT draft extension, allowing Oragono to be integrated with other systems like Jitsi (#948, #1136)
    • Services (NickServ, ChanServ, etc.) now respond to CTCP VERSION messages (#1055, thanks @jesopo!)
    • Added BOT ISUPPORT token, plus a B flag for bots in 352 RPL_WHOREPLY (#1117)
    • Added support for the +T no-CTCP user mode (#1007, thanks @clukawski!)
    • Added support for persisting the realname of always-on clients (#1065, thanks @clukawski!)
    • Added a warning on incorrect arguments to /NICKSERV REGISTER (#1179, thanks @LukeHoersten!)

    Fixed

    • Fixed channels with only invisible users not being displayed in /LIST output (#1161, thanks @bogdomania!)
    • Fixed INVITE not overriding a +b ban (#1168)
    • Fixed incorrect CHGHOST lines during authentication with /NICKSERV IDENTIFY under some circumstances (#1108, thanks Geo-!)
    • Fixed incorrect CHGHOST lines sent to users during connection registration (#1125, thanks @jesopo!)
    • Fixed a race condition where nicknames of signed-out users could remain in the channel names list (#1166, thanks @eskimo!)
    • Fixed the last line of the MOTD being truncated in the absence of a terminating \n (#1167, thanks @eskimo!)
    • Fixed away-notify lines not being sent on channel JOIN (#1198, thanks savoyard!)
    • Fixed incorrect source of some nickserv messages (#1185)
    • Fixed idle time being updated on non-PRIVMSG commands (thanks r3m and @happyhater!)
    • Fixed /NICKSERV UNREGISTER and /NICKSERV ERASE not deleting stored user modes (#1157)

    Security

    • Connections to an STS-only listener no longer reveal the exact server version or server creation time (#802, thanks @csmith!)

    Changed

    • /DLINE now operates on individual client connections (#1135)
    • When using the multiclient feature, each client now has its own independent MONITOR list (#1053, thanks @ajaspers!)
    • MONITOR L now lists the nicknames in the form they were originally sent with MONITOR +, without casefolding (#1083)
    • We now send the traditional 445 ERR_SUMMONDISABLED and 446 ERR_USERSDISABLED in response to the SUMMON and USERS commands (#1078, thanks @KoraggKnightWolf!)
    • RPL_ISUPPORT parameters with no values are now sent without an = (#1067, @1069, #1091, thanks @KoraggKnightWolf and @jesopo!)
    • TAGMSG storage is now controlled via the history.tagmsg-storage config block (#1172)
    • /NICKSERV CERT ADD with no argument now adds the user's current TLS certificate fingerprint, when applicable (#1059, thanks @emersonveenstra!)

    Internal

    • The config file containing recommended defaults is now named default.yaml, instead of oragono.yaml (#1130, thanks @k4bek4be!)
    • The output of the /INFO command now includes the full git hash, when applicable (#1105)
    Source code(tar.gz)
    Source code(zip)
    oragono-2.2.0-rc1-checksums.txt(1.00 KB)
    oragono-2.2.0-rc1-freebsd-386.tar.gz(5.01 MB)
    oragono-2.2.0-rc1-freebsd-x86_64.tar.gz(5.18 MB)
    oragono-2.2.0-rc1-linux-386.tar.gz(5.01 MB)
    oragono-2.2.0-rc1-linux-arm64.tar.gz(4.84 MB)
    oragono-2.2.0-rc1-linux-armv6.tar.gz(4.91 MB)
    oragono-2.2.0-rc1-linux-armv7.tar.gz(4.91 MB)
    oragono-2.2.0-rc1-linux-x86_64.tar.gz(5.20 MB)
    oragono-2.2.0-rc1-macos-x86_64.tar.gz(5.35 MB)
    oragono-2.2.0-rc1-windows-386.zip(5.08 MB)
    oragono-2.2.0-rc1-windows-x86_64.zip(5.27 MB)
  • v2.1.0(Jun 1, 2020)

    We're pleased to announce Oragono 2.1.0, a new stable release.

    Since the release of 2.0.0 in March, a number of new communities and organizations have adopted Oragono as a communications tool. This new release incorporates many improvements and fixes derived from the experiences of real-world operators and end users. Highlights include:

    • Native support for websockets contributed by @hhirtz, eliminating the need for a separate websockets-to-IRC proxy server
    • Tighter control over the relationship between account names and nicknames, eliminating the need for extbans
    • Support for sending account verification emails directly from Oragono, including DKIM signatures

    Many thanks to @ajaspers and @hhirtz for contributing patches, to @ajaspers, @eklitzke, and @hhirtz for contributing code reviews, to @ajaspers, @bogdomania, @clukawski, Csibesz, @csmith, @eklitzke, @nxths, @hhirtz, @jesopo, @jlnt, @justjanne, @jwheare, @k4bek4be, @KoraggKnightWolf, @kula, @kylef, @Mitaka8, @petteri, @PizzaLover2007, @prawnsalad, @RyanSquared, savoyard, and @xPaw for reporting issues, and to @bogdomania, @boppy, Nuve, stickytoffeepuddingwithcaramel, and @vegax87 for contributing translations.

    This release includes changes to the config file format, including one breaking change: support for server.ip-cloaking.secret-environment-variable has been removed. (See below for instructions on how to upgrade if you were using this feature.) All other changes to the config file format are backwards compatible and do not require updating before restart.

    This release includes a database change. If you have datastore.autoupgrade set to true in your configuration, it will be automatically applied when you restart Oragono. Otherwise, you can update the database manually by running oragono upgradedb (see the manual for complete instructions).

    This release includes a change to the MySQL schema. This change will be applied automatically when you restart Oragono. It is fully backwards compatible (i.e., if it is necessary for you to downgrade Oragono back to 2.0.0, it will not be necessary to downgrade the schema).

    Config Changes

    • Added websocket attribute of individual listeners, and a new server.websockets section, for configuring websocket listeners. (#967, thanks @hhirtz!)
    • The recommended default is now to enable IP cloaking. In order to facilitate this, the cloaking secret is now stored in the database, instead of the config file. If you currently have a secret stored in the config file (as server.ip-cloaking.secret), it will be automatically imported into the database. If you were using secret-environment-variable to distribute your cloaking secret, you can import it manually after restart using the new /HOSTSERV SETCLOAKSECRET command. (#952)
    • Added accounts.nick-reservation.force-nick-equals-account, which ensures that logged-in clients are using their account name as their nickname. This eliminates the need for extbans and is a new recommended default. (#864)
    • Added guest-nickname-format and force-guest-format, which optionally add a prefix like Guest- to the nicknames of unauthenticated users (#749)
    • The recommended default is now to enable history storage and playback, with messages expiring after 7 days. (As with all changes in recommended config values, applying this to an existing config file requires explicitly changing the values.) (#1030)
    • Added history.retention section for controlling new features related to history storage and deletion (#858)
    • The recommended default for accounts.multiclient.always-on is now opt-in (#919)
    • Added accounts.default-user-modes; the recommended default is now to set +i on all users automatically (#942, thanks @ajaspers!)
    • Added channels.list-delay, allowing restrictions on channel listings as a defence against spambots (#964)
    • Added accounts.multiclient.auto-away, allowing always-on clients to be automatically marked as away when all their sessions disconnect
    • Added accounts.throttling as a global throttle on the creation of new accounts (#913)
    • New format for accounts.callbacks.mailto, allowing direct email sending and DKIM signing (#921)
    • Added accounts.login-via-pass-command, providing a new mechanism for legacy clients to authenticate to accounts by sending PASS account:password pre-registration (#1020)
    • Added datastore.mysql.socket-path, allowing MySQL connections over UNIX domain sockets (#1016, thanks savoyard and @ajaspers!)
    • Added roleplay section for controlling the server's roleplay features (#865)
    • The recommended default for accounts.nick-reservation.allow-custom-enforcement is now false (#918)
    • The recommended default is now to allow PROXY and WEBIRC lines from localhost (#989, #1011)
    • Added channels.registration.operator-only, optionally restricting channel registrations to operators (#685)
    • Added server.output-path for controlling where the server writes output files (#1004)
    • Operator capability names prefixed with oper: have been normalized to remove the prefix (the old names are still respected in the config file) (#868)
    • The log category names localconnect and localconnect-ip have been changed to connect and connect-ip respectively (the old names are still respected in the config file) (#940)

    Security

    • Fixed incorrect enforcement of ban/invite/exception masks under some circumstances (#983)
    • STATUSMSG were being stored in history without the relevant minimum-prefix information, so they could be replayed to unprivileged users. This was fixed by not storing them at all. (#959, thanks @prawnsalad!)
    • Fixed invisible users not being hidden from WHO * queries (#991, thanks @ajaspers!)
    • Restricted nicknames of some additional common services: OperServ, BotServ, MemoServ, and Global (#1080, thanks @KoraggKnightWolf!)

    Fixed

    • Fixed incorrect rejection of draft/multiline messages containing blank lines (#1005, thanks @jwheare!)
    • Fixed roleplay commands, which were completely broken from v1.1.0 through v2.0.0 (#865, thanks @petteri and @Mitaka8!)
    • Fixed /SAMODE applying user mode changes to the operator instead of the target user (#866, thanks @csmith!)
    • Fixed some channels not being unregistered during account unregistration (#889)
    • Fixed /NICKSERV SET and related commands being unavailable when account registration is disabled (#922, thanks @PizzaLover2007!)
    • Fixed TAGMSG not being replayed correctly in history (#1044)
    • Fixed incorrect 401 ERR_NOSUCHNICK responses on TAGMSG sent to a service (#1051, thanks @ajaspers!)
    • Fixed 301 RPL_AWAY not being sent in WHOIS responses when applicable (#850)
    • /OPER with no password no longer disconnects the client (#951)
    • Fixed failure to send extended-join responses after account unregistration (#933, thanks @jesopo!)
    • Improved validation of channel keys (#1021, thanks @kylef!)
    • Fixed labeling of 421 ERR_UNKNOWNCOMMAND responses (#994, thanks @k4bek4be!)
    • Fixed incorrect parsing of ident protocol responses (#1002, thanks @justjanne!)
    • Fixed registration completing after NICK and an ident response, without waiting for USER (#1057, thanks @KoraggKnightWolf!)
    • Fixed messages rejected by the +R mode being stored in history (#1061, thanks @KoraggKnightWolf!)
    • Fixed redundant /INVITE commands not sending 443 ERR_USERONCHANNEL (#842, thanks @hhirtz!)
    • Fixed /NICKSERV REGISTER response displaying mailto: out of context (#985, thanks @eklitzke!)
    • Fixed nickname changes not sending 731 RPL_MONOFFLINE when appropriate (#1076, thanks @ajaspers!)
    • Fixed incorrect MONITOR responses in some cases (#1086, thanks @ajaspers!)
    • Fixed HostServ approval and rejection notices being sent from the wrong source (#805)
    • Error messages for invalid TLS certificate/key pairs are now more informative (#982)
    • Fixed error message when attempting to attach a plaintext session to an always-on client (#955, thanks @bogdomania and @xPaw!)
    • Increased the TLS handshake timeout, increasing reliability under high CPU contention (#894)
    • Fixed CHANMODES ISUPPORT token (#408, #874, thanks @hhirtz!)
    • Fixed 002 RPL_MYINFO parameters (#1058, thanks @KoraggKnightWolf!)
    • Fixed incorrect parameter limit for MONITOR in the TARGMAX isupport token (#1090, thanks @KoraggKnightWolf!)
    • Fixed edge cases in handling of the +k channel mode parameter (#874, thanks @hhirtz!)
    • account-notify lines are now part of the labeled-response batch when applicable (#1018)
    • Fixed incorrect help description of channel mode +R (#930, thanks @PizzaLover2007!)
    • Fixed 255 RPL_LUSERME response to indicate that the number of federated peer servers is 0 (#846, thanks @RyanSquared!)

    Changed

    • Account names are now permanent identifiers; they cannot be re-registered after unregistration, and applicable nickname protections remain in force. (#793)
    • User modes of always-on clients now persist across server restarts (#819)
    • Registered channels with no members remain present on the server, including their in-memory history messages when applicable (#704, thanks @bogdomania!)
    • Updated the setname IRCv3 capability to its ratified version (#1001)
    • /CHANSERV AMODE now takes immediate effect (#729)
    • The channel founder can now take any action that would require channel privileges without actually having the +q mode (#950, #998)
    • Account unregistration now always disconnects the client (#1028)
    • Fakelag is now temporarily disabled during the sending of a draft/multiline message batch (#817)
    • Failed attempts to join a +R channel now send 477 ERR_NEEDREGGEDNICK (#936, thanks @PizzaLover2007, @jesopo!)
    • 353 RPL_NAMREPLY now always uses a trailing parameter, for compatibility with incorrect client implementations (#854, #862)
    • Channels with persistent history can no longer be renamed with /RENAME (#827)
    • The self-signed certificate generation command oragono mkcerts now generates a 2048-bit RSA certificate, instead of a NIST P-521 ECDSA certificate (#898)
    • Cleaned up compatibility with an obsolete WEBIRC escaping convention (#869)
    • The cloak secret is now stored in the database, so it can no longer be rotated by changing server.ip-cloaking.secret. To rotate the secret, use the new /HOSTSERV SETCLOAKSECRET command. (#952)

    Added

    • Added native support for websockets (#967, thanks @hhirtz!)
    • Added support for sending verification emails directly (i.e., without a MTA/smarthost), including DKIM signing (#920, #921)
    • Added /NICKSERV LIST and /CHANSERV LIST, allowing operators to list registered nicknames and channels (#974, thanks @ajaspers!)
    • Added auto-away feature for marking always-on clients away when all their sessions are disconnected; see accounts.multiclient.auto-away and /NICKSERV HELP SET for more information (#824)
    • Added /HISTSERV PLAY, which plays back history messages as NOTICEs from the HistServ service (#383, thanks @nxths!)
    • Added /HISTSERV DELETE for deleting history messages (see the config option history.retention.allow-individual-delete) (#858)
    • Added /HISTSERV FORGET for deleting all history messages associated with an account (see the config option history.retention.enable-account-indexing) (#858)
    • Added /HISTSERV EXPORT for exporting all history messages associated with an account as JSON. This can be used at the user's request for regulatory compliance reasons (see the config option history.retention.enable-account-indexing) (#858)
    • Added support for logging legacy clients into accounts via the PASS command, with the account:password syntax used by Freenode. To enable this feature, set accounts.login-via-pass-command to true. (#1020, thanks @jlnt!)
    • Added /NICKSERV ERASE as an escape hatch for operators, allowing an account to be erased and re-registered (#793)
    • Added support for playing back MODE and TOPIC messages in history (#532)
    • Added conventional.yaml, a version of the config file that provides a more traditional IRC experience. We recommend a config file based on oragono.yaml for production networks, and one based on conventional.yaml for IRCv3 conformance testing. (#918)
    • Added an optional global throttle on the creation of new accounts (#913)
    • Added support for restricting /LIST responses sent to anonymous clients (#964)
    • Added support for the Plan 9 operating system and its derivatives, including testing on 9front (#1025, thanks @clukawski!)

    Removed

    • Removed support for colored log output (#940, #939)
    • Removed support for distributing the cloaking secret via environment variables (#952)

    Internal

    • make build now includes an abbreviated git hash in the 002 RPL_YOURHOST and 004 RPL_MYINFO version strings, when applicable (#1031)
    • Official releases no longer contain the git hash, only the revision tag (#1031)
    • Official releases are now built with -trimpath (#901)
    Source code(tar.gz)
    Source code(zip)
    oragono-2.1.0-checksums.txt(990 bytes)
    oragono-2.1.0-freebsd-386.tar.gz(4.97 MB)
    oragono-2.1.0-freebsd-x86_64.tar.gz(5.15 MB)
    oragono-2.1.0-linux-386.tar.gz(4.97 MB)
    oragono-2.1.0-linux-arm64.tar.gz(4.80 MB)
    oragono-2.1.0-linux-armv6.tar.gz(4.88 MB)
    oragono-2.1.0-linux-armv7.tar.gz(4.87 MB)
    oragono-2.1.0-linux-x86_64.tar.gz(5.16 MB)
    oragono-2.1.0-macos-x86_64.tar.gz(5.36 MB)
    oragono-2.1.0-windows-386.zip(5.03 MB)
    oragono-2.1.0-windows-x86_64.zip(5.21 MB)
  • v2.1.0-rc1(May 25, 2020)

    We're pleased to be publishing the release candidate for 2.1.0 (the official release should follow in a week or so).

    Since the release of 2.0.0 in March, a number of new communities and organizations have adopted Oragono as a communications tool. This new release incorporates many improvements and fixes derived from the experiences of real-world operators and end users. Highlights include:

    • Native support for websockets contributed by @hhirtz, eliminating the need for a separate websockets-to-IRC proxy server
    • Tighter control over the relationship between account names and nicknames, eliminating the need for extbans
    • Support for sending account verification emails directly from Oragono, including DKIM signatures

    Many thanks to @ajaspers and @hhirtz for contributing patches, to @ajaspers, @eklitzke, and @hhirtz for contributing code reviews, to @ajaspers, @bogdomania, @clukawski, Csibesz, @csmith, @eklitzke, @nxths, @hhirtz, @jesopo, @jlnt, @justjanne, @jwheare, @k4bek4be, @kula, @kylef, @Mitaka8, @petteri, @PizzaLover2007, @prawnsalad, @RyanSquared, savoyard, and @xPaw for reporting issues, and to @bogdomania, @boppy, Nuve, stickytoffeepuddingwithcaramel, and @vegax87 for contributing translations. for contributing translations.

    This release includes changes to the config file format, including one breaking change: support for server.ip-cloaking.secret-environment-variable has been removed. (See below for instructions on how to upgrade if you were using this feature.) All other changes to the config file format are backwards compatible and do not require updating before restart.

    This release includes a database change. If you have datastore.autoupgrade set to true in your configuration, it will be automatically applied when you restart Oragono. Otherwise, you can update the database manually by running oragono upgradedb (see the manual for complete instructions).

    This release includes a change to the MySQL schema. This change will be applied automatically when you restart Oragono. It is fully backwards compatible (i.e., if it is necessary for you to downgrade Oragono back to 2.0.0, it will not be necessary to downgrade the schema).

    Config Changes

    • Added websocket attribute of individual listeners, and a new server.websockets section, for configuring websocket listeners. (#967, thanks @hhirtz!)
    • The recommended default is now to enable IP cloaking. In order to facilitate this, the cloaking secret is now stored in the database, instead of the config file. If you currently have a secret stored in the config file (as server.ip-cloaking.secret), it will be automatically imported into the database. If you were using secret-environment-variable to distribute your cloaking secret, you can import it manually after restart using the new /HOSTSERV SETCLOAKSECRET command. (#952)
    • Added accounts.nick-reservation.force-nick-equals-account, which ensures that logged-in clients are using their account name as their nickname. This eliminates the need for extbans and is a new recommended default. (#864)
    • Added guest-nickname-format and force-guest-format, which optionally add a prefix like Guest- to the nicknames of unauthenticated users (#749)
    • The recommended default is now to enable history storage and playback, with messages expiring after 7 days. (As with all changes in recommended config values, applying this to an existing config file requires explicitly changing the values.) (#1030)
    • Added history.retention section for controlling new features related to history storage and deletion (#858)
    • The recommended default for accounts.multiclient.always-on is now opt-in (#919)
    • Added accounts.default-user-modes; the recommended default is now to set +i on all users automatically (#942, thanks @ajaspers!)
    • Added channels.list-delay, allowing restrictions on channel listings as a defence against spambots (#964)
    • Added accounts.multiclient.auto-away, allowing always-on clients to be automatically marked as away when all their sessions disconnect
    • Added accounts.throttling as a global throttle on the creation of new accounts (#913)
    • New format for accounts.callbacks.mailto, allowing direct email sending and DKIM signing (#921)
    • Added accounts.login-via-pass-command, providing a new mechanism for legacy clients to authenticate to accounts by sending PASS account:password pre-registration (#1020)
    • Added datastore.mysql.socket-path, allowing MySQL connections over UNIX domain sockets (#1016, thanks savoyard and @ajaspers!)
    • Added roleplay section for controlling the server's roleplay features (#865)
    • The recommended default for accounts.nick-reservation.allow-custom-enforcement is now false (#918)
    • The recommended default is now to allow PROXY and WEBIRC lines from localhost (#989, #1011)
    • Added channels.registration.operator-only, optionally restricting channel registrations to operators (#685)
    • Added server.output-path for controlling where the server writes output files (#1004)
    • Operator capability names prefixed with oper: have been normalized to remove the prefix (the old names are still respected in the config file) (#868)
    • The log category names localconnect and localconnect-ip have been changed to connect and connect-ip respectively (the old names are still respected in the config file) (#940)

    Security

    • Fixed incorrect enforcement of ban/invite/exception masks under some circumstances (#983)
    • STATUSMSG were being stored in history without the relevant minimum-prefix information, so they could be replayed to unprivileged users. This was fixed by not storing them at all. (#959, thanks @prawnsalad!)
    • Fixed invisible users not being hidden from WHO * queries (#991, thanks @ajaspers!)

    Fixed

    • Fixed incorrect rejection of draft/multiline messages containing blank lines (#1005, thanks @jwheare!)
    • Fixed roleplay commands, which were completely broken from v1.1.0 through v2.0.0 (#865, thanks @petteri and @Mitaka8!)
    • Fixed /SAMODE applying user mode changes to the operator instead of the target user (#866, thanks @csmith!)
    • Fixed some channels not being unregistered during account unregistration (#889)
    • Fixed /NICKSERV SET and related commands being unavailable when account registration is disabled (#922, thanks @PizzaLover2007!)
    • Fixed TAGMSG not being replayed correctly in history (#1044)
    • Fixed 301 RPL_AWAY not being sent in WHOIS responses when applicable (#850)
    • /OPER with no password no longer disconnects the client (#951)
    • Fixed failure to send extended-join responses after account unregistration (#933, thanks @jesopo!)
    • Improved validation of channel keys (#1021, thanks @kylef!)
    • Fixed labeling of 421 ERR_UNKNOWNCOMMAND responses (#994, thanks @k4bek4be!)
    • Fixed incorrect parsing of ident protocol responses (#1002, thanks @justjanne!)
    • Fixed redundant /INVITE commands not sending 443 ERR_USERONCHANNEL (#842, thanks @hhirtz!)
    • Fixed /NICKSERV REGISTER response displaying mailto: out of context (#985, thanks @eklitzke!)
    • Fixed HostServ approval and rejection notices being sent from the wrong source (#805)
    • Error messages for invalid TLS certificate/key pairs are now more informative (#982)
    • Fixed error message when attempting to attach a plaintext session to an always-on client (#955, thanks @bogdomania and @xPaw!)
    • Increased the TLS handshake timeout, increasing reliability under high CPU contention (#894)
    • Fixed CHANMODES ISUPPORT token (#408, #874, thanks @hhirtz!)
    • Fixed edge cases in handling of the +k channel mode parameter (#874, thanks @hhirtz!)
    • account-notify lines are now part of the labeled-response batch when applicable (#1018)
    • Fixed incorrect help description of channel mode +R (#930, thanks @PizzaLover2007!)
    • Fixed 255 RPL_LUSERME response to indicate that the number of federated peer servers is 0 (#846, thanks @RyanSquared!)

    Changed

    • Account names are now permanent identifiers; they cannot be re-registered after unregistration, and applicable nickname protections remain in force. (#793)
    • User modes of always-on clients now persist across server restarts (#819)
    • Registered channels with no members remain present on the server, including their in-memory history messages when applicable (#704, thanks @bogdomania!)
    • Updated the setname IRCv3 capability to its ratified version (#1001)
    • /CHANSERV AMODE now takes immediate effect (#729)
    • The channel founder can now take any action that would require channel privileges without actually having the +q mode (#950, #998)
    • Account unregistration now always disconnects the client (#1028)
    • Fakelag is now temporarily disabled during the sending of a draft/multiline message batch (#817)
    • Failed attempts to join a +R channel now send 477 ERR_NEEDREGGEDNICK (#936, thanks @PizzaLover2007, @jesopo!)
    • Channels with persistent history can no longer be renamed with /RENAME (#827)
    • The self-signed certificate generation command oragono mkcerts now generates a 2048-bit RSA certificate, instead of a NIST P-521 ECDSA certificate (#898)
    • Cleaned up compatibility with an obsolete WEBIRC escaping convention (#869)
    • The cloak secret is now stored in the database, so it can no longer be rotated by changing server.ip-cloaking.secret. To rotate the secret, use the new /HOSTSERV SETCLOAKSECRET command. (#952)

    Added

    • Added native support for websockets (#967, thanks @hhirtz!)
    • Added support for sending verification emails directly (i.e., without a MTA/smarthost), including DKIM signing (#920, #921)
    • Added /NICKSERV LIST and /CHANSERV LIST, allowing operators to list registered nicknames and channels (#974, thanks @ajaspers!)
    • Added auto-away feature for marking always-on clients away when all their sessions are disconnected; see accounts.multiclient.auto-away and /NICKSERV HELP SET for more information (#824)
    • Added /HISTSERV PLAY, which plays back history messages as NOTICEs from the HistServ service (#383, thanks @nxths!)
    • Added /HISTSERV DELETE for deleting history messages (see the config option history.retention.allow-individual-delete) (#858)
    • Added /HISTSERV FORGET for deleting all history messages associated with an account (see the config option history.retention.enable-account-indexing) (#858)
    • Added /HISTSERV EXPORT for exporting all history messages associated with an account as JSON. This can be used at the user's request for regulatory compliance reasons (see the config option history.retention.enable-account-indexing) (#858)
    • Added support for logging legacy clients into accounts via the PASS command, with the account:password syntax used by Freenode. To enable this feature, set accounts.login-via-pass-command to true. (#1020, thanks @jlnt!)
    • Added /NICKSERV ERASE as an escape hatch for operators, allowing an account to be erased and re-registered (#793)
    • Added support for playing back MODE and TOPIC messages in history (#532)
    • Added conventional.yaml, a version of the config file that provides a more traditional IRC experience. We recommend a config file based on oragono.yaml for production networks, and one based on conventional.yaml for IRCv3 conformance testing. (#918)
    • Added an optional global throttle on the creation of new accounts (#913)
    • Added support for restricting /LIST responses sent to anonymous clients (#964)
    • Added support for the Plan 9 operating system and its derivatives, including testing on 9front (#1025, thanks @clukawski!)

    Removed

    • Removed support for colored log output (#940, #939)
    • Removed support for distributing the cloaking secret via environment variables (#952)

    Internal

    • make build now includes an abbreviated git hash in the 002 RPL_YOURHOST and 004 RPL_MYINFO version strings, when applicable (#1031)
    • Official releases no longer contain the git hash, only the revision tag (#1031)
    • Official releases are now built with -trimpath (#901)
    Source code(tar.gz)
    Source code(zip)
    oragono-2.1.0-rc1-checksums.txt(1.00 KB)
    oragono-2.1.0-rc1-freebsd-386.tar.gz(4.96 MB)
    oragono-2.1.0-rc1-freebsd-x86_64.tar.gz(5.14 MB)
    oragono-2.1.0-rc1-linux-386.tar.gz(4.96 MB)
    oragono-2.1.0-rc1-linux-arm64.tar.gz(4.79 MB)
    oragono-2.1.0-rc1-linux-armv6.tar.gz(4.86 MB)
    oragono-2.1.0-rc1-linux-armv7.tar.gz(4.86 MB)
    oragono-2.1.0-rc1-linux-x86_64.tar.gz(5.15 MB)
    oragono-2.1.0-rc1-macos-x86_64.tar.gz(5.34 MB)
    oragono-2.1.0-rc1-windows-386.zip(5.01 MB)
    oragono-2.1.0-rc1-windows-x86_64.zip(5.20 MB)
  • v2.0.0(Mar 8, 2020)

    We're pleased to announce Oragono 2.0.0, a major update with a wide range of enhancements and fixes. Highlights include:

    • Support for storing chat history in a MySQL backend
    • Full "bouncer" functionality, including "always-on" clients that remain present on the server even when disconnected
    • LDAP support contributed by @mattouille
    • Support for the ratified labeled-response IRCv3 capability
    • Enhanced support for Kubernetes
    • Many new service commands, improving management of client certificates, vhosts, and channel ownership

    Many thanks to @csmith, @mattouille, and @xPaw for contributing patches, to @csmith and @wrmsr for contributing code reviews, to @bogdomania, @brenns10, @daurnimator, @ekianjo, horseface, @ivucica, @jesopo, @jwheare, KoDi, lover, @notbandali, @poVoq, @TETYYS, and @zaher for reporting issues, and to @bogdomania and Nuve for contributing translations.

    This release includes changes to the config file format, including two breaking changes:

    1. Backwards compatibility with the old server.listen format for configuring listeners has been removed; you must now use the server.listeners format that was introduced in 1.2.0.
    2. The two sections server.connection-limits and server.connection-throttling have been consolidated into one new section, server.ip-limits.

    Other changes to the config file format are backwards compatible and do not require updating before restart. To minimize potential downtime, we suggest the following workflow:

    1. Without upgrading your oragono binary, edit your config file to add new server.listeners and server.ip-limits sections, based on the example config file
    2. Rehash your server, confirming that the new config file is valid for for the previous version of the server
    3. Upgrade your oragono binary to the new 2.0.x version and restart your server
    4. Once your deployment is stable on 2.0.x, delete the old server.listen, server.connection-limits, and server.connection-throttling sections from your config, and rehash your server to confirm

    This release includes a database change. If you have datastore.autoupgrade set to true in your configuration, it will be automatically applied when you restart Oragono. Otherwise, you can update the database manually by running oragono upgradedb (see the manual for complete instructions).

    Config Changes

    • Desupported server.listen in favor of server.listeners, a breaking change (#794)
    • Desupported server.connection-limits and server.connection-throttling in favor of server.ip-limits, a breaking change (#646)
    • The recommended default is now to allow plaintext only on loopback interfaces (#801)
    • Added server.casemapping option to control which Unicode nicknames and channels are allowed (#693)
    • Added server.lookup-hostnames and server.forward-confirm-hostnames options to control hostname lookup (#688)
    • Added new limits.multiline section to control the new draft/multiline capability
    • Added sections for enabling the optional MySQL history storage backend: datastore.mysql for connecting to the server and history.persistent for controlling which messages are stored
    • Added history.restrictions for preventing people from retrieving arbitrarily old history messages
    • Added history.znc-maxmessages, allowing a higher history replay limit for bouncer emulation relative to CHATHISTORY
    • Added accounts.vhosts.offer-list, allowing users to take pre-approved vhosts without operator approval (#737)
    • Renamed accounts.bouncer to accounts.multiclient (the old name still works) (#787)
    • New recommended values of server.max-sendq, server.ip-cloaking.num-bits, accounts.registration.bcrypt-cost, accounts.nick-reservation.enabled (now true), accounts.multiclient.allowed-by-default (now true)
    • Added server.ip-cloaking.secret-environment-variable, allowing the cloaking secret to be deployed via an environment variable for use in Kubernetes (#741, thanks @daurnimator!)

    Security

    • Added forward confirmation of reverse DNS lookups for hostnames: to enable this, set server.forward-confirm-hostnames to true (#688)
    • Added protection against confusable channel names (#581)
    • Fixed cases where Tor users could receive CTCP messages, contrary to expectations (#752, #753)
    • Fixed NS INFO displaying the local timezone (#710)
    • Fixed accounts.authentication-enabled failing to disable the NS IDENTIFY command (#721)

    Added

    • Added support for persistent history storage in MySQL (#348)
    • Added support for "always-on" clients that remain present on the server even when disconnected (#348, #701)
    • Added support for LDAP (#690, thanks @mattouille, @ivucica, and @mabgnu!)
    • Added support for the new draft/multiline specification (#670, thanks @jwheare and @jesopo!)
    • Added new modes for Unicode characters in nicknames and channel names: ASCII-only and "permissive" (allowing emoji) (#693)
    • Added support for plaintext PROXY lines ahead of a TLS handshake, improving compatibility with some Kubernetes load balancers (#561, thanks @RyanSquared and @daurnimator!)
    • Added support for authenticating operators by TLS client certificates, and automatically applying operator privileges on login (#696, thanks @RyanSquared!)
    • Added /DEOPER command to remove operator privileges (#549, thanks @bogdomania!)
    • Added /CHANSERV TRANSFER, allowing transfers of channel ownership (#684)
    • Added /NICKSERV CERT, allowing users to manage their authorized client certificates (#530)
    • Added /HOSTSERV TAKE, allowing users to take pre-approved vhosts without operator approval (#737)
    • Added support for configuring connection limits and throttling for individual CIDRs (#646, thanks KoDi!)
    • Added /CHANSERV PURGE, allowing server administrators to shut down channels (#683)
    • Added /CHANSERV CLEAR, allowing channel founders to reset stored bans and privileges (#692)
    • Added /CHANSERV SET, allowing channel founders to disable channel history (#379)
    • Added account preference AUTOREPLAY-JOINS, allowing greater control over when joins and parts appear in history replay (#616, thanks @zaher!)
    • Added /DEBUG CRASHSERVER command (#791)
    • znc.in/playback now supports nicknames as targets (#830)
    • Added channel mode +C to suppress CTCP messages to a channel (#756)
    • Added some missing snomasks for events related to accounts and vhosts (+s v to enable vhost snomasks) (#347, #103)

    Changed

    • Updated CHATHISTORY support to the latest draft (#621, thanks @prawnsalad!)
    • Updated to the ratified labeled-response specification from the earlier draft/labeled-response-0.2 (#757)
    • /HISTORY now defaults to returning 100 messages, and also takes time durations like 1h as arguments (#621, thanks lover!)
    • D-Lines are no longer enforced against loopback IPs (#671)
    • Password length limit was reduced from 600 bytes to 300 bytes (#775)

    Fixed

    • Fixed a bug where znc.in/playback commands would play every channel, regardless of the target parameter (#760, thanks @brenns10!)
    • Fixed MODE -o not removing all operator permissions (#725, #549, thanks @bogdomania!)
    • Fixed client-only tags being relayed in direct messages to users without the message-tags capability (#754, thanks @jesopo!)
    • Fixed the channel user limit (the +l mode) not persisting after server restart (#705, thanks @bogdomania!)
    • Fixed response to JOIN lines with parameters ending in a comma (#679, thanks @bogdomania!)
    • Fixed confusable protection not being removed from unregistered accounts (#745, thanks @bogdomania!)
    • Fixed rehash not enabling nickname reservation, vhosts, or history under some circumstances (#702, thanks @bogdomania!)
    • Fixed responses to the USERHOST command (#682)
    • Fixed bad results when running oragono upgradedb against a missing database file (#715, thanks @bogdomania!)
    • Fixed confusing NS GHOST behavior when nickname reservation is disabled (#727, thanks horseface!)
    • Fixed validation of authzid during SASL (#716, thanks @xPaw!)
    • Non-ASCII characters are proactively disallowed in ip-cloaking.netname (#713, thanks @bogdomania!)
    • Limited the time during which znc.in/playback affects channel joins (#829)

    Removed

    • Removed oragono.io/maxline-2 capability in favor of the new draft/multiline capability (#670, #752)
    • Removed oragono.io/bnc capability (multiclient functionality is now controllable only via server config and /NS SET MULTICLIENT) (#787)
    • Removed draft/acc capability and related ACC command (#723)

    Internal Notes

    • Updated to Go 1.14 and modules, simplifying the build process (#699)
    Source code(tar.gz)
    Source code(zip)
    oragono-2.0.0-checksums.txt(979 bytes)
    oragono-2.0.0-freebsd-i386.tar.gz(4.78 MB)
    oragono-2.0.0-freebsd-x64.tar.gz(4.96 MB)
    oragono-2.0.0-linux-arm64.tar.gz(4.62 MB)
    oragono-2.0.0-linux-armv6.tar.gz(4.68 MB)
    oragono-2.0.0-linux-armv7.tar.gz(4.68 MB)
    oragono-2.0.0-linux-i386.tar.gz(4.78 MB)
    oragono-2.0.0-linux-x64.tar.gz(4.98 MB)
    oragono-2.0.0-osx-x64.tar.gz(5.16 MB)
    oragono-2.0.0-windows-i386.zip(4.85 MB)
    oragono-2.0.0-windows-x64.zip(5.06 MB)
  • v2.0.0-rc1(Mar 2, 2020)

    We're pleased to be publishing the release candidate for Oragono 2.0.0 (the official release should follow in a week or two). Version 2.0.0 is a major update with a wide range of enhancements and fixes. Major highlights include:

    • Support for storing chat history in a MySQL backend
    • Full "bouncer" functionality, including "always-on" clients that remain present on the server even when disconnected
    • LDAP support contributed by @mattouille
    • Support for the ratified labeled-response IRCv3 capability
    • Enhanced support for Kubernetes

    Many thanks to @csmith, @mattouille, and @xPaw for contributing patches, to @csmith and @wrmsr for contributing code reviews, to @bogdomania, @brenns10, @daurnimator, @ekianjo, horseface, @ivucica, @jesopo, @jwheare, KoDi, lover, @mabgnu, @poVoq, @TETYYS, and @zaher for reporting issues, and to @bogdomania and Nuve for contributing translations.

    This release includes changes to the config file format, including two breaking changes:

    1. Backwards compatibility with the old server.listen format for configuring listeners has been removed; you must now use the server.listeners format that was introduced in 1.2.0.
    2. The two sections server.connection-limits and server.connection-throttling have been consolidated into one new section, server.ip-limits.

    Other changes to the config file format are backwards compatible and do not require updating before restart. To minimize potential downtime, we suggest the following workflow:

    1. Without upgrading your oragono binary, edit your config file to add new server.listeners and server.ip-limits sections, based on the example config file
    2. Rehash your server, confirming that the new config file is valid for for the previous version of the server
    3. Upgrade your oragono binary to the new 2.0.x version and restart your server
    4. Once your deployment is stable on 2.0.x, delete the old server.listen, server.connection-limits, and server.connection-throttling sections from your config, and rehash your server to confirm

    This release includes a database change. If you have datastore.autoupgrade set to true in your configuration, it will be automatically applied when you restart Oragono. Otherwise, you can update the database manually by running oragono upgradedb (see the manual for complete instructions).

    Config Changes

    • Desupported server.listen in favor of server.listeners, a breaking change (#794)
    • Desupported server.connection-limits and server.connection-throttling in favor of server.ip-limits, a breaking change (#646)
    • The recommended default is now to allow plaintext only on loopback interfaces (#801)
    • Added server.casemapping option to control which Unicode nicknames and channels are allowed (#693)
    • Added server.lookup-hostnames and server.forward-confirm-hostnames options to control hostname lookup (#688)
    • Added new limits.multiline section to control the new draft/multiline capability
    • Added sections for enabling the optional MySQL history storage backend: datastore.mysql for connecting to the server and history.persistent for controlling which messages are stored
    • Added history.restrictions for preventing people from retrieving arbitrarily old history messages
    • Added history.znc-maxmessages, allowing a higher history replay limit for bouncer emulation relative to CHATHISTORY
    • Added accounts.vhosts.offer-list, allowing users to take pre-approved vhosts without operator approval (#737)
    • Renamed accounts.bouncer to accounts.multiclient (the old name still works) (#787)
    • New recommended values of server.max-sendq, server.ip-cloaking.num-bits, accounts.registration.bcrypt-cost, accounts.nick-reservation.enabled (now true), accounts.multiclient.allowed-by-default (now true)
    • Added server.ip-cloaking.secret-environment-variable, allowing the cloaking secret to be deployed via an environment variable for use in Kubernetes (#741, thanks @daurnimator!)

    Security

    • Added forward confirmation of reverse DNS lookups for hostnames: to enable this, set server.forward-confirm-hostnames to true (#688)
    • Added protection against confusable channel names (#581)
    • Fixed cases where Tor users could receive CTCP messages, contrary to expectations (#752, #753)
    • Fixed NS INFO displaying the local timezone (#710)
    • Fixed accounts.authentication-enabled failing to disable the NS IDENTIFY command (#721)
    • Fixed confusable protection not being applied to newly registered accounts (#745, thanks @bogdomania!)

    Added

    • Added support for persistent history storage in MySQL (#348)
    • Added support for "always-on" clients that remain present on the server even when disconnected (#348, #701)
    • Added support for LDAP (#690, thanks @mattouille, @ivucica, and @mabgnu!)
    • Added support for the new draft/multiline specification (#670, thanks @jwheare and @jesopo!)
    • Added new modes for Unicode characters in nicknames and channel names: ASCII-only and "permissive" (allowing emoji) (#693)
    • Added support for plaintext PROXY lines ahead of a TLS handshake, improving compatibility with some Kubernetes load balancers (#561, thanks @RyanSquared and @daurnimator!)
    • Added support for authenticating operators by TLS client certificates, and automatically applying operator privileges on login (#696, thanks @RyanSquared!)
    • Added /DEOPER command to remove operator privileges (#549, thanks @bogdomania!)
    • Added /CHANSERV TRANSFER, allowing transfers of channel ownership (#684)
    • Added /NICKSERV CERT, allowing users to manage their authorized client certificates (#530)
    • Added /HOSTSERV TAKE, allowing users to take pre-approved vhosts without operator approval (#737)
    • Added support for configuring connection limits and throttling for individual CIDRs (#646, thanks KoDi!)
    • Added /CHANSERV PURGE, allowing server administrators to shut down channels (#683)
    • Added /CHANSERV CLEAR, allowing channel founders to reset stored bans and privileges (#692)
    • Added /CHANSERV SET, allowing channel founders to disable channel history (#379)
    • Added account preference AUTOREPLAY-JOINS, allowing greater control over when joins and parts appear in history replay (#616, thanks @zaher!)
    • Added /DEBUG CRASHSERVER command (#791)
    • znc.in/playback now supports nicknames as targets (#830)
    • Added channel mode +C to suppress CTCP messages to a channel (#756)
    • Added some missing snomasks for events related to accounts and vhosts (+s v to enable vhost snomasks) (#347, #103)

    Changed

    • Updated CHATHISTORY support to the latest draft (#621, thanks @prawnsalad!)
    • Updated to the ratified labeled-response specification from the earlier draft/labeled-response-0.2 (#757)
    • /HISTORY now defaults to returning 100 messages, and also takes time durations like 1h as arguments (#621, thanks lover!)
    • D-Lines are no longer enforced against loopback IPs (#671)
    • Password length limit was reduced from 600 bytes to 300 bytes (#775)

    Fixed

    • Fixed a bug where znc.in/playback commands would play every channel, regardless of the target parameter (#760, thanks @brenns10!)
    • Fixed MODE -o not removing all operator permissions (#725, #549, thanks @bogdomania!)
    • Fixed client-only tags being relayed in direct messages to users without the message-tags capability (#754, thanks @jesopo!)
    • Fixed the channel user limit (the +l mode) not persisting after server restart (#705, thanks @bogdomania!)
    • Fixed response to JOIN lines with parameters ending in a comma (#679, thanks @bogdomania!)
    • Fixed confusable protection not being removed from unregistered accounts (#745, thanks @bogdomania!)
    • Fixed rehash not enabling nickname reservation, vhosts, or history under some circumstances (#702, thanks @bogdomania!)
    • Fixed responses to the USERHOST command (#682)
    • Fixed bad results when running oragono upgradedb against a missing database file (#715, thanks @bogdomania!)
    • Fixed confusing NS GHOST behavior when nickname reservation is disabled (#727, thanks horseface!)
    • Fixed validation of authzid during SASL (#716, thanks @xPaw!)
    • Non-ASCII characters are proactively disallowed in ip-cloaking.netname (#713, thanks @bogdomania!)
    • Limited the time during which znc.in/playback affects channel joins (#829)

    Removed

    • Removed oragono.io/maxline-2 capability in favor of the new draft/multiline capability (#670, #752)
    • Removed oragono.io/bnc capability (multiclient functionality is now controllable only via server config and /NS SET MULTICLIENT) (#787)
    • Removed draft/acc capability and related ACC command (#723)

    Internal Notes

    • Updated to Go 1.14 and modules, simplifying the build process (#699)
    Source code(tar.gz)
    Source code(zip)
    oragono-2.0.0-rc1-checksums.txt(1019 bytes)
    oragono-2.0.0-rc1-freebsd-i386.tar.gz(4.78 MB)
    oragono-2.0.0-rc1-freebsd-x64.tar.gz(4.96 MB)
    oragono-2.0.0-rc1-linux-arm64.tar.gz(4.62 MB)
    oragono-2.0.0-rc1-linux-armv6.tar.gz(4.68 MB)
    oragono-2.0.0-rc1-linux-armv7.tar.gz(4.68 MB)
    oragono-2.0.0-rc1-linux-i386.tar.gz(4.78 MB)
    oragono-2.0.0-rc1-linux-x64.tar.gz(4.98 MB)
    oragono-2.0.0-rc1-osx-x64.tar.gz(5.17 MB)
    oragono-2.0.0-rc1-windows-i386.zip(4.85 MB)
    oragono-2.0.0-rc1-windows-x64.zip(5.06 MB)
  • v1.2.0(Nov 16, 2019)

    We're pleased to announce Oragono 1.2.0. This version contains bug fixes and minor improvements.

    Many thanks to @bogdomania, @csmith, @edmund-huber, @jesopo, @jwheare, @poVoq, @prawnsalad, and stealthgin for reporting issues and contributing code reviews, and also to @bogdomania, Forbidden (cptbl00dra1n), Nuve, @streaps, and UnLokitoFeliz for contributing translations.

    This release includes a change to the config file format: the old server.listen format for configuring listeners has been replaced by a new server.listeners format. See the bundled oragono.yaml configuration file for a commented example. For now, Oragono maintains backwards compatibility with the old format. To minimize potential downtime, we recommend the following workflow:

    1. Without rewriting your config file, upgrade your oragono binary to the new 1.2.x version and restart your server
    2. Rewrite your configuration file to use the new server.listeners format
    3. Rehash your server, confirming that the rewritten config file is valid and correct

    This release includes a database change. If you have datastore.autoupgrade set to true in your configuration, it will be automatically applied when you restart Oragono. Otherwise, you can update the database manually by running oragono upgradedb (see the manual for complete instructions).

    Config Changes

    • Replaced server.listen section with server.listeners; see oragono.yaml for a commented example (#565)
    • Added history.autoresize_window for automatically resizing history buffers (#349)

    Added

    • Added STS-only listeners; you can configure port 6667 so that it "redirects" clients to TLS on port 6697. See the manual for details. (#448)
    • Added the CHANLIMIT ISUPPORT token (#625, thanks @poVoq!)
    • Added ban creator and creation time to banlist output (#644, thanks stealthgin!)

    Changed

    • Upgraded to the new draft/labeled-response-0.2 capability (#555)
    • oragono mkcerts no longer overwrites existing certificate files (#622, thanks @poVoq!)
    • Allowed Tor and non-Tor connections to attach to the same nickname via bouncer functionality (#632)

    Fixed

    • Fixed CAP LS 302 response being potentially truncated (#594, #661)
    • Fixed redundant output to some MODE commands (#649)
    • Improved display of replies to /msg NickServ verify in some clients (#567, thanks @edmund-huber!)
    • Improved display of NickServ timeout warnings in some clients (#572, thanks @bogdomania!)
    • LUSERS output is now sent at the end of connection registration (#526)
    • Fixed operators not being able to WHOIS some Unicode nicknames (#331, thanks @bogdomania!)
    • Fixed RESUME not clearing the BRB reason (#592, thanks @jesopo!)
    • Fixed an edge case where the BRB timestamp wasn't reset correctly (#642)
    • Fixed behavior of SAMODE issued against a different user (#585)
    • Fixed a false-positive error logline (#601)
    • oragono.io/bnc is no longer advertised when disabled in the config (#595)
    • Made the connection limiter and throttler more resilient against the failure to whitelist a reverse proxy IP (#197, thanks @prawnsalad!)

    Internal Notes

    • Official builds now use Go 1.13, which includes native TLS 1.3 support (#626)
    • Minor performance improvements (#640, #615)
    Source code(tar.gz)
    Source code(zip)
    oragono-1.2.0-checksums.txt(979 bytes)
    oragono-1.2.0-freebsd-i386.tar.gz(4.38 MB)
    oragono-1.2.0-freebsd-x64.tar.gz(4.55 MB)
    oragono-1.2.0-linux-arm64.tar.gz(4.22 MB)
    oragono-1.2.0-linux-armv6.tar.gz(4.29 MB)
    oragono-1.2.0-linux-armv7.tar.gz(4.28 MB)
    oragono-1.2.0-linux-i386.tar.gz(4.37 MB)
    oragono-1.2.0-linux-x64.tar.gz(4.56 MB)
    oragono-1.2.0-osx-x64.tar.gz(4.74 MB)
    oragono-1.2.0-windows-i386.zip(4.45 MB)
    oragono-1.2.0-windows-x64.zip(4.64 MB)
  • v1.2.0-rc1(Nov 4, 2019)

    We're pleased to be publishing the release candidate for 1.2.0 (the official release should follow in a week or two). This version contains bug fixes and minor improvements.

    Many thanks to @bogdomania, @csmith, @edmund-huber, @jesopo, @jwheare, @poVoq, @prawnsalad, and stealthgin for reporting issues and contributing code reviews, and also to @bogdomania, Forbidden (cptbl00dra1n), Nuve, @streaps, and UnLokitoFeliz for contributing translations.

    This release includes a change to the config file format: the old server.listen format for configuring listeners has been replaced by a new server.listeners format. See the bundled oragono.yaml configuration file for a commented example. For now, Oragono maintains backwards compatibility with the old format. To minimize potential downtime, we recommend the following workflow:

    1. Without rewriting your config file, upgrade your oragono binary to the new 1.2.x version and restart your server
    2. Rewrite your configuration file to use the new server.listeners format
    3. Rehash your server, confirming that the rewritten config file is valid and correct

    This release includes a database change. If you have datastore.autoupgrade set to true in your configuration, it will be automatically applied when you restart Oragono. Otherwise, you can update the database manually by running oragono upgradedb (see the manual for complete instructions).

    Config Changes

    • Replaced server.listen section with server.listeners; see oragono.yaml for a commented example (#565)
    • Added history.autoresize_window for automatically resizing history buffers (#349)

    Added

    • Added STS-only listeners; you can configure port 6667 so that it "redirects" clients to TLS on port 6697. See the manual for details. (#448)
    • Added the CHANLIMIT ISUPPORT token (#625, thanks @poVoq!)
    • Added ban creator and creation time to banlist output (#644, thanks stealthgin!)

    Changed

    • Upgraded to the new draft/labeled-response-0.2 capability (#555)
    • oragono mkcerts no longer overwrites existing certificate files (#622, thanks @poVoq!)
    • Allowed Tor and non-Tor connections to attach to the same nickname via bouncer functionality (#632)

    Fixed

    • Fixed CAP LS 302 response being potentially truncated (#594)
    • Fixed redundant output to some MODE commands (#649)
    • Improved display of replies to /msg NickServ verify in some clients (#567, thanks @edmund-huber!)
    • Improved display of NickServ timeout warnings in some clients (#572, thanks @bogdomania!)
    • LUSERS output is now sent at the end of connection registration (#526)
    • Fixed operators not being able to WHOIS some Unicode nicknames (#331, thanks @bogdomania!)
    • Fixed RESUME not clearing the BRB reason (#592, thanks @jesopo!)
    • Fixed an edge case where the BRB timestamp wasn't reset correctly (#642)
    • Fixed behavior of SAMODE issued against a different user (#585)
    • Fixed a false-positive error logline (#601)
    • oragono.io/bnc is no longer advertised when disabled in the config (#595)
    • Made the connection limiter and throttler more resilient against the failure to whitelist a reverse proxy IP (#197, thanks @prawnsalad!)

    Internal Notes

    • Official builds now use Go 1.13, which includes native TLS 1.3 support (#626)
    • Minor performance improvements (#640, #615)
    Source code(tar.gz)
    Source code(zip)
    oragono-1.2.0-rc1-checksums.txt(1019 bytes)
    oragono-1.2.0-rc1-freebsd-i386.tar.gz(4.37 MB)
    oragono-1.2.0-rc1-freebsd-x64.tar.gz(4.54 MB)
    oragono-1.2.0-rc1-linux-arm64.tar.gz(4.22 MB)
    oragono-1.2.0-rc1-linux-armv6.tar.gz(4.28 MB)
    oragono-1.2.0-rc1-linux-armv7.tar.gz(4.27 MB)
    oragono-1.2.0-rc1-linux-i386.tar.gz(4.37 MB)
    oragono-1.2.0-rc1-linux-x64.tar.gz(4.56 MB)
    oragono-1.2.0-rc1-osx-x64.tar.gz(4.73 MB)
    oragono-1.2.0-rc1-windows-i386.zip(4.45 MB)
    oragono-1.2.0-rc1-windows-x64.zip(4.64 MB)
  • v1.1.1(Jul 21, 2019)

    Oragono 1.1.1 is a bugfix release for flaws in message handling, including one with security implications.

    Many thanks to @streaps for reporting issues.

    Upgrade notes

    This release does not change the database or configuration file format.

    Security

    • Previous releases of Oragono would incorrectly relay chat messages containing the \r byte. An attacker could use this to spoof protocol messages from the server (depending on the implementation of the victim's client). This has been fixed. (#610)

    Fixed

    • Fixed incorrect rejection of messages with multiple spaces (#602, thanks @streaps!)
    Source code(tar.gz)
    Source code(zip)
    oragono-1.1.1-checksums.txt(979 bytes)
    oragono-1.1.1-freebsd-i386.tar.gz(4.27 MB)
    oragono-1.1.1-freebsd-x64.tar.gz(4.45 MB)
    oragono-1.1.1-linux-arm64.tar.gz(4.14 MB)
    oragono-1.1.1-linux-armv6.tar.gz(4.20 MB)
    oragono-1.1.1-linux-armv7.tar.gz(4.20 MB)
    oragono-1.1.1-linux-i386.tar.gz(4.27 MB)
    oragono-1.1.1-linux-x64.tar.gz(4.47 MB)
    oragono-1.1.1-osx-x64.tar.gz(4.66 MB)
    oragono-1.1.1-windows-i386.zip(4.35 MB)
    oragono-1.1.1-windows-x64.zip(4.55 MB)
Owner
Oragono
A modern IRC server written in Go.
Oragono
go irc client for twitch.tv

go-twitch-irc This is an irc client for connecting to twitch. It handles the annoying stuff like irc tag parsing. I highly recommend reading the docum

gempir 248 Aug 2, 2022
The Tenyks IRC bot.

Tenyks is a computer program designed to relay messages between connections to IRC networks and custom built services written in any number of languages.

Kyle Terry 173 Jul 27, 2022
This is my first IRC bot for launch ddos attack, Write on Go language.

This is my first IRC bot for launch ddos attack, Write on Go language. For education purpose only. Please test it on your lab, And i create this for join university in the future not for attack anyone server with out any permission!!!

null 0 Oct 24, 2021
IRC bot for launch ddos attack, Mainly of scan target are IoT device that run linux and open default SSH port

This is my first IRC bot for launch ddos attack, Mainly of scan target are IoT device that run linux and open default SSH port, This bot is write on Go language. For education purpose only. Please test it in your lab. And i create this for join university in the future not for attack anyone server with out any permission!!!

Bozer 1 Aug 10, 2022
Jaken - A general purpose IRC bot featuring user acls and arbitrary plugins

Design principles This bot is based on the premise of a loosely coupling between

Lex van Roon 2 Jul 21, 2022
The modern cryptocurrency trading bot written in Go.

bbgo A trading bot framework written in Go. The name bbgo comes from the BB8 bot in the Star Wars movie. aka Buy BitCoin Go! Current Status Features E

Yo-An Lin 660 Aug 11, 2022
Open-IM-Server is open source instant messaging Server.Backend in Go.

Open-IM-Server Open-IM-Server: Open source Instant Messaging Server Instant messaging server. Backend in pure Golang, wire transport protocol is JSON

OpenIM Corporation 8.9k Aug 12, 2022
Fastest light-weight Discord server joiner written in GO

DiscordInviterGO! Fastest light-weight Discord server joiner written in GO Disclaimer For Educational purposes only. Use at your own risk. Automation

Vanshaj 88 Aug 9, 2022
WIP Telegram Bot API server in Go

botapi The telegram-bot-api, but in go. WIP. Reference: https://core.telegram.org/bots/api Reference implementation: https://github.com/tdlib/telegram

gotd 14 Jun 12, 2022
A simple Discord bot developed for the Bedrock Gophers discord server.

Bedrock Gopher A simple Discord bot developed for the Bedrock Gophers discord server. Click here to invite the bot to your guild. You will also need t

Dragonfly 3 Mar 12, 2022
This utility allows you to execute Minecraft server commands through the RCON protocol via Telegram chat.

Minecraft RCON by Telegram This utility allows you to execute Minecraft server commands through the RCON protocol via Telegram chat. FAQ When you run

Alexander Pers0na2 4 Jul 24, 2022
CoachCarter: a discord bot which lets a server know if its inactive for too long

I took this job because I wanted to affect change in a special group of young me

Waqas Ali 1 Jan 7, 2022
RaunchBot brings you the latest Raunchy content straight to your favorite Discord server.

RaunchBot RaunchBot brings you the latest Raunchy content straight to your favorite Discord server. Development: Compile and run the project. TOKEN=ab

null 1 Jan 22, 2022
RaunchBot brings you the latest Raunchy content straight to your favorite Discord server.

RedditBot RedditBot brings you the latest Raunchy content straight to your favorite Discord server. Get RedditBot in your discord here. Bot Commands:

null 1 Jan 22, 2022
Bot to automatically approve Bitbucket Server PRs

renovate-approve-bot-bitbucket-server Introduction This is a small application, similar to renovatebot/renovate-approve-bot-bitbucket-cloud to automat

Swisscom 1 Feb 9, 2022
This is a program that auctions minecraft names, its self hostable and can be used via your server.

Auction-Bot This is a discord bot made in go, its a wip and will be updated over time. This bot atm can create channels in your discord for users to p

null 1 Feb 13, 2022
Simple yet customizable bot framework written in Go.

Introduction Sarah is a general-purpose bot framework named after the author's firstborn daughter. This comes with a unique feature called "stateful c

Go Hagiwara 246 Aug 17, 2022
Slack bot core/framework written in Go with support for reactions to message updates/deletes

Overview Requirements Features Demo The Name Concepts Create Your Own Slackscot Assembling the Parts and Bringing Your slackscot to Life Configuration

Alexandre Normand 52 Jul 6, 2022
A general-purpose bot library inspired by Hubot but written in Go. :robot:

Joe Bot ?? A general-purpose bot library inspired by Hubot but written in Go. Joe is a library used to write chat bots in the Go programming language.

Joe Bot 451 Aug 10, 2022