SSH

Secure-shell access to the same ANSI menus you'd get via Telnet.
Port 2234/tcp by default (deliberately not 22, so it can't
conflict with the box's real system SSH daemon).

Connect

ssh -p 2234 username@bbs.a-net.fyi

Replace hostname / port to match your BBS.

Why SSH over telnet?

• Encrypted in transit
• The SSH client's own username/password prompt IS the BBS login —
  whatever you type there is captured and used to auto-login into the
  menu system, no second prompt
• Public-key auth is intentionally disabled server-side (the BBS needs
  a real password to auto-login with, and public-key auth would skip
  that step) — any client falls back to password auth automatically
• Some networks block port 23 outright; SSH usually gets through

What you can do over SSH

Everything the Telnet menus offer. Doors work over SSH too,
including DOS doors via the DosBridge — the bridge is
protocol-agnostic.

Host key

The first connection prompts you to accept the BBS's host key
fingerprint. The sysop should publish the fingerprint somewhere
(usually on one of their info pages) so you can verify it.