SSH

Secure-shell access to the same ANSI menus you'd get via Telnet.
Port 22/tcp.

Connect

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

Replace hostname / port to match your BBS.

Why SSH over telnet?

• Encrypted in transit
• Auth handled by SSH before you ever see the BBS menu — username
  pre-fills, optional password is also accepted
• Public-key auth works for accounts that have one registered
• Some networks block port 23 outright; SSH usually gets through

SSH key auth

Register your public key from /profile/edit → SSH Keys.
Multiple keys per user are fine. Key auth bypasses the password
prompt.

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 the info pages) so you can verify it.