Notices
Behaviour that changed underneath you. Nothing to run, but worth reading before you update.
- warningFrom this release on, an update checks the release's signature itself, before any of the new release's code runs, and refuses a stable release that is not signed by the Canectic release key. That check needs gpg: sudo apt install gnupg (already in the install instructions). Without it your next update is refused and says what to install. System Info shows whether gpg is there, under External programs.
Canectic BBS v0.9.20b
A security fix for updates, so update soon. Also: newsletters, polls, a Top 10 page on the website, and Ctrl keys, ; commands and global commands for terminal menus.
Released 2026-10-23 (Carrier).
Highlights
Updates you can trust. Your board now checks a release's signature itself, with the release key it already has, before any of the new release's code runs, and refuses a stable release that the Canectic release key did not sign. Until now the new release's own updater did the check, so a release built by someone else could have left it out. Your board also keeps its own list of the release keys it trusts, which no release can change without a signature by a key it already trusts; hears of a revoked key before a release signed with it arrives; and trusts a second key, kept offline in reserve. All of this protects the updates after this one.
Newsletters. Publish your own, or follow one a network publishes, FidoNews for one, from its echo or its file echo. Readers find the issues on the website and the terminal, newest first, and can have each new one sent to them by email or netmail. One written here can go out to the network too, posted into an echo and hatched into a file echo.
Polls. The voting booth: ask your callers a question, on the website, in a block on the home page or in the web call flow, and on the terminal, where a login stage asks each poll waiting for the caller's vote. One vote an account, which can be changed until the poll closes. Only the counts are ever shown.
New kinds of hotkey for terminal menus. A hotkey can be Ctrl and a letter, or a word typed after a ;, such as ;NODESPY, so sysop commands need not use up a key. Global commands work on every menu, shown on them or not.
Install and update without the release site. A new board can be installed from the release archive alone, as a file echo delivers it, and an update that changes no Node packages no longer needs the internet.
Upgrading
From 0.9.19b the update applies itself, and quickly: new tables for newsletters and polls, two new menu columns and one wider one, nothing redrawn. Worth knowing:
- Install
gpgif your board does not have it:sudo apt install gnupg(it has always been in the install instructions). This update is still checked the old way, but every update after it checks the signature itself, and withoutgpgit is refused, saying what to install. System Info shows whethergpgis there, under External programs. - When it checks for updates, and just before it applies one, your board now also asks keys.openpgp.org about the release keys. Set
update_keyserver_url(Configuration, Updates) blank to stop it; the release site and the release file echo still bring news of the keys. - Nothing new appears until you set it up. Newsletters and polls are under Content. Add their links under Menus > Web Navigation, their blocks under Content > Home Page or in the web call flow, and the Newsletters and Polls commands to your terminal menus. Top 10 has a page of its own now too, with a link to add the same way.
- A menu hotkey longer than one character, such as
^N, never worked before and works now, as Ctrl+N. Look over your menus if you ever saved one. Your menus are otherwise unchanged: Node Spy becomes the global command;SPYonly on a new board, and you can add;SPYyourself under Menus > Global Commands.
Coming from 0.9.18b 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.19b release notes, https://canectic.tranqsoft.com/releases/0.9.19b/notes, which point further back.
Changes
Security
- Fixed: an update could install a release that did not come from us. The release's signature was checked by the release's own updater, so a release built by someone else could leave the check out, and an unsigned release was accepted unless you had turned on
update_require_signature. Anyone able to put a release on the release site, or into the release file echo, could have had their code run by a sysop pressing Update. Your board now checks the signature itself, with the release key it already has, before any of the new release's code runs. A stable release that is not signed by the release key is refused whatever the setting; a development build may still be unsigned on a board on the development channel with the setting off. An archive holding files outside the signed list is refused too, and so is a genuine older release offered as a newer one. This protects every update from this release on: the update to this release is still checked the old way. - New: a revoked release key reaches your board before a release signed with it does. Your board now looks for news of the Canectic release keys on every update check and again just before applying an update: on the release site, on a keyserver (
update_keyserver_url, keys.openpgp.org; HTTP only, blank turns it off), and in the release file echo, where a key file is taken the moment it is tossed. A revocation used to reach a board only inside a later release, after the release it was meant to stop. When your board learns of one it tells you, and refuses releases signed with that key. See Release keys indocs/sysop/UPDATES.md. - Fixed: one release could change which release key a board trusts. A board trusted the key in its installed key file, which every update replaces, so a release signed with a stolen signing key could leave a board trusting a key of the thief's choosing, for good. A board now keeps its own list of the release keys it trusts, in
.canectic-trust/, which no update replaces, and a release can change it only through a signature by a key the board already trusts. Everything the board learns about those keys is kept, so a revoked key stays revoked. - New: a second release key, kept in reserve. If the key that signs releases ever has to be revoked, the reserve signs from then on and your board carries on updating, rather than having nothing left it trusts. It is kept offline and has never been on the machine that builds releases. Your board starts trusting it by itself, because the current release key has vouched for it; its fingerprint is
DE1A 1F1F E233 5146 64DE 7113 8ABB 2D2E C0D1 3127, listed indocs/sysop/INSTALL.mdbeside the current one.
Updates
- New: an update that changes no Node packages needs no internet. It used to run
npm installagainst the npm registry every time. A board with no internet, taking its releases down the file echo, can now update whenever the packages have not changed, and the Update page andupdate.jssay beforehand whether a release changes them (Packages: unchanged or changed). One that does needs the registry, or a mirror set in.npmrc. - Fixed: a release that arrived down the release file echo was never offered. The update check looked for the file in the wrong directory, so a board taking its releases over FTN never saw one.
Installing
- New: install from the release archive alone.
bootstrap.sh --from DIRused to need the index, metadata and checksum list beside the archive, which a file echo does not deliver. Given the archive alone, it now checks theMANIFESTsigned inside it, then every file against thatMANIFEST, refusing anything that does not match or is not listed, before running anything from it. Upper-cased names are fine. See Installing from the archive alone indocs/sysop/INSTALL.md. - Changed: a first install checks the release keys on a keyserver, and needs
gpg. The bootstrap looks the release keys up on keys.openpgp.org first, so a key revoked since it was written is refused, and stops if it cannot ask (--no-keyserveronce you have compared the fingerprint yourself). It now refuses a release whose signature it cannot check at all, where it used to carry on with a warning;gpghas always been in the install instructions.
Newsletters
- New: newsletters (#108). A newsletter is written on your board, or taken from where a network publishes one: an echo (the messages of a named poster, or every message, with numbered parts such as FidoNews's "[00/06]" to "[06/06]" joined back into one issue) or a file echo (the text in each file hatched there, FidoNews's
FNEWTH42.ZIPfor one). Readers find the issues on the website at/newslettersand on the terminal (menu command Newsletters, with a lightbar to pick newsletters and issues), newest first with back issues kept, and a home page block and a login stage show the newest issue when it is new since their last visit. Readers can ask for each new issue by email or netmail, to a verified address, with the notification sending switched on. An issue written here can also be posted into an echo, in parts when it is long, and hatched into a file echo as an 8.3 ZIP with a FILE_ID.DIZ. Set them up under Content > Newsletters; seedocs/sysop/NEWSLETTERS.md.
Polls
- New: polls (#13), the voting booth. A question with up to 20 answers, one to choose or several, voted on from the website at
/polls, from a Polls block on the home page or in the web call flow (voted in without leaving the page), and on the terminal (menu command Polls, and a login stage that asks each poll waiting for the caller's vote). Each account has one vote, which it can change until the poll closes. A poll can let callers add answers of their own, closes when you say, and shows its results after people vote or only once it closes. Only counts are ever shown: who voted for what is shown to nobody, sysops included. Set them up under Content > Polls, where you can also let callers start polls of their own (sysops only until you do); seedocs/sysop/POLLS.md.
Top 10 Lists
- New: a Top 10 page on the website, and a link to it for the navigation bar.
/toptenshows every list with someone on it, with buttons for the last 7 days, the last 30 days and all time, and each list opens on its own page with all 25 it keeps. Add it to the bar under Menus > Web Navigation, A page on this board, Top 10. The lists used to be on the website only as home page or call flow blocks. - Fixed: the terminal's Top 10 lists said only "7 3 A period" at the bottom. They now name each period beside its key,
7 Last 7 days 3 Last 30 days A All time, with the one on screen marked, and Left and Right change the period too.
Menus
- Fixed: a menu hotkey of more than one character never worked, including Ctrl keys written as
^N: the editor took 1 to 4 characters, but the menu matched only one typed key. An entry saved as^Nworks now, as Ctrl+N, without being changed. - New: Ctrl keys and ; commands as hotkeys. Beside each entry's hotkey, choose Key, Ctrl + (a letter pressed with Ctrl, shown as
^N) or ; command (the caller types;, a word of up to 12 letters or digits, and Enter, such as;NODESPY), so sysop commands need not use up a key. A caller with no ; command they may use gets no prompt when they press;. Ctrl keys a terminal uses for something else (H, I, J, M) are refused, and S, Q and C saved with a warning. - New: global commands. Entries that work in every menu, set up once from the Global Commands card on Menus > Menu Editor. Each is shown on every menu or works everywhere without being shown; a menu's own entry with the same hotkey wins in that menu. See Global Commands in
docs/sysop/MENUS.md. - Changed: on a new board, Node Spy is the global command
;SPY, for sysops only, in place of N on the starter Main menu, so it takes no key a caller could want. Boards already set up keep their menus as they are; add;SPYunder Global Commands if you want it.
Notifications
- Fixed: Up and Down did not move the bar in the terminal's notification list, so only the first notification could be opened. They do now.
- Version
- 0.9.20b
- 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-unused0011-doorserver-collections0012-time-online-totals0013-activity-log0014-redraw-message-html0015-redraw-file-descriptions0016-menu-hotkey-width- SHA-256
22e5d09e7b9a578e50bed9c1e95dc1a892e7ca08b3530e28157bfb10b5e5a01f- Files
- metadata·manifest