Stable release

v0.9.13aHandshake

Released 2026-09-29, 25.0 MB.

Notices

Behaviour that changed underneath you. Nothing to run, but worth reading before you update.

  • infoThis release closes a hole that let anyone who could reach your board's web address start your door games. The door server is now off until you turn on doorserver_enabled, only BBSes you register can connect, and they can run only the doors you mark Available to Door Server. If you deactivated the Doorserver pool under Admin > Flows to close the hole, you can leave it that way, or make it active again before switching the door server on. See docs/sysop/DOORSERVER.md.
  • infoIf freq_filebox_dir is still ftn/filebox (the old default), your board serves file requests (FREQ) from the same directory that holds per-peer outbound fileboxes, so any file left at its top level can be requested by any system you link with. New installs now use a separate ftn/freq, which this update creates; your setting is not changed. To separate them, move the files you mean to offer into ftn/freq and set freq_filebox_dir to ftn/freq under Paths on the Configuration page.
  • infoMessages that arrived in UTF-8 without saying so were stored garbled before this release (’ as ΓÇÖ, Jörg as J├╢rg, Cyrillic and Hebrew as runs of box drawing), including messages imported from JAM bases. New mail is read correctly from now on. To repair what is already stored, run node src/tools/maintenance.js --fix-charset --dry-run with the worker running to see what would change in each area, then without --dry-run to repair it. ANSI art and other genuine CP437 text is left alone. The old text is kept, so node src/tools/maintenance.js --revert-charset puts it all back.

Canectic BBS v0.9.13a

Closes a hole that let anyone who could reach your board's web address start your door games, adds a working door server, and reads mail written in UTF-8 correctly. Every board should take this release.

Released 2026-09-29 (Handshake).

Highlights

Nobody can start your door games from outside any more. The door server connection accepted a login published with the source code and ran any door it was asked for. It is now off until you switch it on, and even then only BBSes you have registered can connect, and only to the doors you choose.

A working door server. Offer your doors to other BBSes, let verified users register their own boards for your approval, and send your callers to another Canectic board's doors from a menu entry. Other BBS software connects with a one-file client, or over RLogin if you switch it on.

Mail written in UTF-8 no longer arrives garbled (’ as ΓÇÖ, Jörg as J├╢rg), and --fix-charset repairs what is already stored, with a way back.

Mailer fixes: a peer using EMSI was sent the same mail on every session, file attachments on netmail were never sent, and file requests to a system outside zone 1 never went out.

Changing where a file area's files are kept now moves them, instead of leaving the area looking empty.

Dates on the web read the same way on every page, in your board's time, and opening the notification bell marks your notifications read.

Upgrading

From 0.9.12a the update applies itself. Worth knowing afterwards:

  • The door server is off until you turn on doorserver_enabled. If you deactivated the Doorserver pool under Admin > Flows to close the hole on 0.9.12a, you can leave it that way, or make it active again before switching the door server on. See docs/sysop/DOORSERVER.md.
  • Repair garbled messages already stored: node src/tools/maintenance.js --fix-charset --dry-run with the worker running shows what would change in each area; run it again without --dry-run to repair them. ANSI art and genuine CP437 text are left alone, and --revert-charset puts everything back.
  • If freq_filebox_dir is still ftn/filebox, any file at the top of that directory can be requested by any system you link with, because it also holds the per-peer outbound fileboxes. Move the files you mean to offer into ftn/freq, which this update creates, and set freq_filebox_dir to ftn/freq under Paths on the Configuration page.
  • The netmail_in and netmail_out tables are removed if they are empty. If yours hold anything, the update keeps them and says so.

Coming from 0.9.11a or earlier? The notes for the releases you skip apply to you too. The Update page lists every one that concerns your board before you update, and they are in the 0.9.12a release notes, https://canectic.tranqsoft.com/releases/0.9.12a/notes.

Changes

Security

  • Updated morgan, multer and nodemailer for three published advisories: forged lines in the web access log, disk space left behind by uploads that were abandoned partway, and, on a board that sends email through more than one mail server, TLS connections to one server named as another.
  • Fix: anyone who could reach your board's web address could start any of your door games. The door server connection (/ws/doorserver), meant for other BBSes to send their callers to your doors, accepted a built-in test login that was published with the source code, and then ran whatever door it was asked for. It now refuses every connection unless you switch the door server on (doorserver_enabled, off by default), no remote system can log in until you register it, and a remote caller can only run a door you have marked as available to the door server. If you want to close it on a board you have not updated yet, deactivate the Doorserver pool under Admin > Flows and restart the gateway.
  • Fix: failed logins from mail clients and rejected API tokens could not be banned by fail2ban. A wrong IMAP or SMTP password was logged without the caller's address, and an API request with a bad token was not logged at all. Both are now written to security.log with the address, in the form the shipped filter in examples/fail2ban/ already matches, and each line now says which service it came from (via IMAP, via SMTP, via API). A wrong current password when changing your password, on the web or in the terminal, is logged the same way. No change to the filter is needed.

Networking

  • Fix: on a board running as a single process (PROCESS_MODE=embedded), outbound FTN mail waited for the next scheduled scan, and connecting to a system from the nodelist did nothing. The mail process ignored both requests. It now handles them as the standalone mailer does.
  • Fix: netmail your board relayed carried a Via line with no version, just "Canectic", and the system statistics page and the terminal's system information showed the version as blank. Both now show the version the board is running.
  • Fix: mail written in UTF-8 by software that does not say so arrived garbled, with ’ stored as ΓÇÖ, Jörg as J├╢rg, and whole Cyrillic or Hebrew passages unreadable. A message without a character set declaration was always read as CP437. It is now read as UTF-8 when that is what it contains, which genuine CP437 text, box drawing and ANSI art included, never is. Message bases imported from JAM files are read the same way. Messages already stored garbled can be repaired, see below.
  • Fix: names and subjects with accented or other non-English letters were mangled on arrival. The To, From and Subject lines of FTN mail lost the top bit of every such character. They are now read in the same character set as the message.
  • Fix: netmail to RaidFix was accepted and then silently dropped, with no reply. It is now answered by FileFix, since RAID's RaidFix is its file echo manager.
  • Removed: the tic_auto_forward setting, which did nothing (received TIC files are always passed on to the systems subscribed to that area), and the unused netmail_in and netmail_out tables from before netmail moved into private mail. The tables are only dropped when empty; if yours hold anything, the update keeps them and says so.
  • Fix: a file attached to FTN netmail was never sent. The netmail went out marked as carrying a file, but the file itself was not queued for the mailer, so the recipient got a message referring to an attachment that never arrived. The attachment now goes with the next mail session.
  • Fix: a peer using EMSI (Wazoo) was sent the same mail on every session. After a Wazoo session sent a file, nothing marked it as sent: packets were not deleted and flow file lines were not marked done, so the next session offered them again. EMSI sessions now clean up exactly as binkp ones do. Mail received over EMSI is also tossed as soon as the session ends, rather than waiting for the next scheduled toss.
  • Fix: a file request (FREQ) to a system outside zone 1 was never sent, and the Request Files form on the FREQ page did nothing at all for a host or hub address (node 0, such as 2:203/0). The request was written to the zone 1 outbound whatever the address, where no session for that system looks, and it ignored MAILER_OUTBOUND_DIR. Requests now go to the outbound the mailer reads for that address. A second request to the same system before it has been sent is now added to the first rather than replacing it.
  • The FREQ filebox now has its own directory, ftn/freq, on new installs. It used to default to ftn/filebox, which also holds the per-peer outbound fileboxes, so any file left at the top of ftn/filebox could be requested by any system you link with. Existing boards keep their setting; see the upgrade note to move yours.

Administration

  • New: a working door server. Other BBSes can now send their callers to the doors you choose. Mark a door "Available to Door Server" in its settings, switch on doorserver_enabled, and add each BBS under Doors > Door Server; it gets a System ID and a secret, shown once. Any verified user can also register their BBS from the Doors page (doorserver_register_security, which by default is the verified level). Each registration waits for your approval and they are notified when you decide, except for users whose security reaches doorserver_auto_approve_security or who hold a flag listed in doorserver_auto_approve_flags, whose registrations are approved at once. You can suspend a BBS, give it a new secret, or limit how many of its callers can be on at once (doorserver_max_concurrent). Remote callers appear in your caller log with their BBS's name. Sysops of other BBS software connect with doorclient.js, one file needing only Node 22 or later, which they download from the Door Server page and run as a door; it reads the caller's name from DOOR32.SYS or DOOR.SYS and lets them pick a door or go straight to one. Your own callers can visit another Canectic board's doors too: register your board there, add it under Door Server > Remote door servers (the Test button checks the connection and lists its doors), and add a menu entry with the command Remote Door Server. For BBS software that can open RLogin connections but cannot run the client, switch on doorserver_rlogin_enabled (off by default; port doorserver_rlogin_port, 5513) and restart: the RLogin user is SYSTEMID:username, the password field is the secret, and the terminal type names the door (or ansi for the list).
  • Fix: an API token issued from Admin > API Tokens was never shown, so it could not be used; tokens are stored only as a hash, so it could not be recovered either. The token is now shown once when it is issued. Messages after saving a file group (such as a file move starting) were not shown either and now are.
  • Fix: the First Message Post, Nth Message Post, First File Upload and Nth File Upload template events never fired, so a template attached to one was never sent. They now fire when a user posts a message (on the web, in the terminal or in a QWK reply packet) or uploads a file. Each user's count starts from what your board already held, so nobody with a posting history is greeted as a first-time poster; messages that arrived from a network are never counted.
  • Fire Template Event is now in the menu editor's Command list. A menu entry could already fire a message template event, but the editor did not offer the command, so it had to be added by importing menu JSON. Its argument box suggests the event codes your board has.

Messages

  • Fix: in the terminal message reader, D (delete) and M (move) did nothing for a moderator reading a message full screen, although the bottom bar offered them. They now work there. In the thread list M is Mark Read, as before.

Maintenance

  • Fix: running node src/tools/maintenance.js --regen-html again while one was still going ignored the second request, including its --area, --width and --batch, although the tool said those areas had been queued. A request with different options now queues behind the first; an identical one joins it, and the tool now says already running rather than claiming to have queued it. The same applied to regenerating private mail or file descriptions, purging PM trash or tossed packets with a different --days, and a --dry-run of rethreading or MSGID repair queued alongside a real one.
  • Fix: --regen-html --dry-run was not a dry run. The option never reached the worker, so it regenerated every message for real, and it counted every message as updated either way. A dry run now writes nothing and reports, area by area, how many messages would change, with a few message ids to look at first. A real run now only rewrites messages whose display actually changes. The same goes for --regen-pm-html.
  • Fix: a maintenance or toss job that ran past its time limit was reported failed but carried on running, and the next job started alongside it. Such a job is now asked to stop: regenerating message HTML, MSGID repair and rethreading stop at the next safe point, and the job is reported as stopped. A job that cannot stop is logged as still running, and the worker health check keeps showing it until it ends. The health check also measured every job against the toss limit (30 minutes), so a maintenance job that was healthy but ran longer than that could get the worker restarted under it; each job is now measured against its own queue's limit.
  • New: repair messages stored garbled by the character set problem above. node src/tools/maintenance.js --fix-charset --dry-run reports, area by area, how many messages are affected and a few message ids to look at; without --dry-run it repairs them, including names and subjects, and redraws them on the web. ANSI art and other genuine CP437 text is left alone. The old text is kept, so --revert-charset puts everything back. Add --area SHORTCODE to do one area at a time.
  • Regenerating message HTML now runs one area at a time, from the command line and from the admin Events page. A large board could not finish in a single job before maintenance_job_timeout (60 minutes) stopped it, so it had to be done by hand in --area batches. The command waits until every area is done, however long that takes, and reports each one as it finishes.

Files

  • Changing where a file area's files are kept now moves them. Changing a file group's base directory, a file area's directory, or the file base directory on the Configuration page used to leave every file behind at the old path, so the areas looked empty. Saving such a change now shows which areas are affected, where their files are and where they would go, and asks whether to move them. They are moved in the background, one at a time, and you get a notification when it is done. A file whose name is already at the new location is left where it is and listed, never overwritten.
  • Fix: a file area directory set to a full path (starting with / or ~/) was put inside the group's directory anyway. It is now used as given, like a group's base directory, and moving the group leaves it alone.
  • Fix: file requests (FREQ) never found files held in file areas. Only the FREQ filebox and magic names worked. Files in the areas a linked system is subscribed to can now be requested.

Web

  • Dates on the user side of the web read the same way everywhere, in your board's time. Profile, notifications, last callers, announcements, the call flow, the maintenance page and the maintenance banner used to show each viewer's own 12-hour date format, differently on each page. They now use the board's clock and one style: a bare time today (17:30), Yesterday 17:30, 3 days ago through the week, then Sep 25, and Dec 25, 2025 once it is more than six months back. Hover over one for the exact time. Tables you can sort by date keep the full date and time.
  • Opening the notification bell now marks your notifications read. The badge clears as soon as you look, rather than staying lit until you clicked each one or pressed Mark All Read, which is gone from the dropdown (the full Notifications page still has it). New ones stay highlighted until you close the dropdown.
  • New private mail no longer shows in the notification bell on the web, since the mail icon already counts it. Callers still see new mail in the terminal's notification list, and reading or deleting the message, on the web, in the terminal, in a mail client or in a QWK packet, now clears it there.
  • Fix: finishing the web call flow, or posting to the wall from it, returned an error when the request carried no form data. Browsers always send some, so this was only seen from scripts; the call flow now finishes normally either way.
Version
0.9.13a
Channel
Stable
Node
22.0.0 or later
Upgrades from
0.9.0a or later
Migrations
0001-menu-layout0002-msgid-tuple-split0003-qwk-conference-blocks0004-settings-provenance0005-refresh-stale-version0006-normalise-body-text0007-netmail-seenby-text0008-qnet-role-dirs0009-user-activity-counts0010-retire-unused
SHA-256
26b109b8af7d87df57f8da2982c3559447b002e5fa6a0fe53bc9b8b5b95ca11e
Files
metadata·manifest