What it is
bbs.kbve.com is a terminal front door to kbve.com. Callers read and post on
the message boards, chat with #general on the IRC network, and play six door
games. Everyone arrives as a guest; signing in is a one-time code shown on the
terminal and redeemed at kbve.com/bbs/ with a browser session, through
POST /api/v1/bbs/claim.
How to connect
| Public port | Pod port | Protocol | For |
|---|---|---|---|
| 22 | 2222 | SSH | any terminal: ssh bbs.kbve.com |
| 6400 | 6400 | telnet | PETSCII, Commodore 64 terminals |
| 6401 | 6401 | telnet | ANSI terminals without SSH |
ports: above is the record: version-sync’s check-manifests fails CI when
the load balancer or the deployment disagrees with it.
SSH is the way in for anyone who can use it; telnet stays for the machines that cannot. Port 23 is closed: CERT-Bund flagged it as open telnet, and a port-23 scan is what finds a board, so the ANSI board answers on 6401 only.
The SSH host key is SHA256:kTn9PVNarl0UWjpJ5J5gIIGS+a0N7F8YEXaFzorJBu8
(ED25519), declared as ssh_host_key: above. Check it against what your client
prints on first connect. The key lives in the kbve-bbs-ssh-host-key
SealedSecret and is read from BBS_SSH_HOST_KEY_FILE; without that file the
board makes a key at start-up, and every restart would trip known_hosts for
every caller. The deployment passes the declared fingerprint as
SSH_HOST_KEY_FINGERPRINT, and the board refuses to serve SSH under any other
key, so a resealed or swapped key cannot go out without the doc changing too.
The front door
The first screen names nothing past the welcome: whatever answers a connection is what internet scanners index. A caller presses H to show they are human before the menu draws. Five other keys, Q, or 30 seconds of silence ends the call, so a scanner cannot hold one of the 64 session slots. Telnet callers are told their line is not encrypted; SSH callers are not.
Signing in by SSH key
Any key, or none, gets a caller in as a guest. A caller who signs in with the
claim code while connected with a key is offered to remember it; from then on
ssh <handle>@bbs.kbve.com with that key goes straight to the menu, past the
human check.
- The handle in the SSH login name says who the caller claims to be; the key proves it. Keys are matched against that one account, so no reverse lookup of key to user exists.
- Remembered keys are SHA-256 fingerprints in the user’s
app_metadata.bbs_ssh_keys, written through the GoTrue admin API. Only the service role writesapp_metadata, so nobody can attach a key to another account, and it needs no migration. GoTrue copiesapp_metadatainto every token it signs, so an account keeps at most five. Account forgets them all. - When an account has keys, a non-matching key is turned away so the client tries its next, which lets the remembered key sit anywhere in an agent.
- Keyless clients get in through keyboard-interactive with no prompts.
- A client that asks to run a command, as Warp’s SSH wrapper does, gets the board as if it had asked for a shell. Input in the first moment of a channel is dropped so a wrapper’s bootstrap is not read as keypresses.
- Port forwarding, agent forwarding and subsystems are refused.
Doors
Nothing behind a door is saved yet. Dungeons and Dope Wars ask before Q ends a run in progress; the quick games leave on the first press.
Where the boards come from
The forum service. The BBS holds no forum code: it lists spaces, threads and
comments through /api/v1/forum/*, and posts through the forum’s service
routes with the service key, so a post made from a terminal is filed, tagged
and stored by the same functions as one made on the site.
One replica
Sign-in codes, who is online and the IRC relay live in the process, so the
deployment runs exactly one pod, and /api/v1/bbs must reach the same pod as
the listeners.
Releasing
Bump version: above, and nothing else: sh tools/version-sync/sync.sh bump kbve-bbs <next> writes it and version.toml. The kbve-bbs job stamps
Cargo.toml from it and publishes the image, and kbve-bbs-deploy opens the
merge request that repoints kbve-bbs-deployment.yaml. Cut the bump from the
default branch’s current version: a newer bump supersedes an older one still
queued, and a bump that lands below a published tag publishes nothing.
Discuss on the forum
Questions, fixes and notes on this page live in the KBVE forum.