dum-dum-irc 0.4.0.post1

A non-standard internet relay chat program.

dum-dum-irc

A handcrafted implementation of an internet relay chat without following any conventions or RFC standards.

Changelog | Contributing Guide

Usage

With Python 3.11+ installed, you can get the currently stable version on PyPI:

pip install dum-dum-irc

Or if you have Git, you can install the latest in-development version:

pip install git+https://github.com/thegamecracks/dum-dum-irc

Once installed, the dumdum and dumdum-server entry points should be provided. Run dumdum-server --help for options.

Implementation

Dumdum consists of two parts:

1. The Sans-IO protocol, defined in dumdum.protocol
2. The asyncio wrapper, defined in dumdum.client and dumdum.server

The Sans-IO protocol is responsible for handling the generation and consumption of byte streams, along with producing events from received messages, while the asyncio wrapper is responsible for the actual network communication between the server and its clients.

Protocol

Clients are able to send the following messages:

1. HELLO: 0x00 | 1-byte version
2. AUTHENTICATE: 0x02 | varchar nickname (32)
3. SEND_MESSAGE: 0x03 | varchar channel name (32) | varchar content (1024)
4. LIST_CHANNELS: 0x04
5. LIST_MESSAGES: 0x05 | 8-byte before snowflake or 0 | 8-byte after snowflake or 0

Servers are able to send the following messages:

1. HELLO: 0x00 | 0 or 1 using SSL
2. INCOMPATIBLE_VERSION: 0x01 | 1-byte version
3. ACKNOWLEDGE_AUTHENTICATION: 0x02 | 0 or 1 success
4. SEND_MESSAGE: 0x03 | 8-byte snowflake | varchar channel name (32) | varchar nickname (32) | varchar content (1024)
5. LIST_CHANNELS: 0x04 | 2-byte length | varchar channel name (32) | ...
6. LIST_MESSAGES: 0x05 | 3-byte length | same fields after SEND_MESSAGE | ...

Clients must send a HELLO command and wait for the server to respond with HELLO. Afterwards the client must send an AUTHENTICATE command and wait for a successful ACKNOWLEDGE_AUTHENTICATION before they can begin chat communications.

When the client disconnects and reconnects, they MUST re-send hello and re-authenticate with the server.

If the server supports SSL, they can set using SSL in HELLO to indicate that the client should upgrade the connection to SSL. At this point, the protocol should not receive any data until after the SSL handshake is complete.

As this protocol has been intentionally designed to be simple (no timeouts or keep alives), I/O wrappers do not need a significant amount of work to implement it.

TLS Encryption

dumdum-server can use SSL certificates to encrypt connections. For example, if you want to use a self-signed certificate and private key, you can install OpenSSL and run the following command:

openssl req -new -x509 -days 365 -nodes -out dumdum.crt -keyout dumdum.key

After filling out (or skipping) the certificate signing request prompts, you can then run the server with the resulting dumdum.crt and dumdum.key files:

dumdum-server --cert dumdum.crt:dumdum.key

As for the dumdum client, SSL can be enabled by the user before connecting to a server. If the server uses a self-signed certificate, the user will need to download the server's certificate (.crt) and select it.