Releases

Download Canectic

Canectic BBS, and Canectic Monitor, the desktop app that tells a sysop what is happening on the board. Every release is signed and checksummed.

Canectic BBS, latest stable

v0.9.20bCarrier

Released 2026-10-23, 27.5 MB, needs Node 22.0.0 or later.

SHA-256
22e5d09e7b9a578e50bed9c1e95dc1a892e7ca08b3530e28157bfb10b5e5a01f
Files
metadata·manifest·SHA256SUMS·signature
Canectic Monitor

v0.1.0

A desktop app for the sysop's own computer. It plays a sound, and can put up a notification, for what happens on the board: a caller connecting or logging in, a new user, mail for the sysop, and more. It needs a board release newer than 0.9.16b and an API token with the Sysop Monitor scope.

Released 2026-10-08.What changed

Linux (64-bit)
11.3 MB, needs glibc 2.38 or later
Windows (64-bit)
11.5 MB, needs Windows 10 or later
Files
metadata·SHA256SUMS

Development

Cut when there is something worth having. Each is a delta against the stable it names, goes through the same release machinery, and is meant to run on live boards. A system on stable is never offered these.

VersionDateTypeSizeNeeds
0.9.20b.20261104
Carrier
2026-11-04delta on 0.9.20b2.0 MBNode 22.0.0+Downloadmetadata
Verifying a download

SHA256SUMS lists every published file, the monitor's included, and SHA256SUMS.asc is a detached signature over it. The chain runs signature, then checksum list, then metadata, then artifact, and the bootstrap checks every link. By hand:

bash
gpg --verify SHA256SUMS.asc SHA256SUMS
sha256sum -c --ignore-missing SHA256SUMS

Signing key fingerprint
F3F1 6D36 59AF 25FB F947 4C6D B5D8 AB14 3016 761F

Over FTN

Boards with an FTN link can receive releases down a file echo, with no outbound HTTP at all. Each archive carries a signed MANIFEST inside it, which is what verifies a release that arrived that way.

CANECTICRelease announcements and support
CANECTIC_FILESStable releases
CANECTIC_DEVDevelopment builds