A great trick arrives with one bad flag.
ASCII Theater turns a terminal into a text movie screen. The site currently advertises Kung Fury and gives visitors one SSH command. That command sets StrictHostKeyChecking=no.[1]
The visual idea rules. The connection advice does not. OpenSSH says no or off can allow a connection to continue when a host key changed. The exact behavior has restrictions, but the useful warning is weakened.[2]
The projector can be weird. The identity check should be boring.
Seeing a key is not verifying a key.
We queried watch.ascii.theater with ssh-keyscan at 11:03 UTC. The server offered one 3072-bit RSA key. Its SHA-256 fingerprint was YMc7KTNDH9riqnd3TGJN0OrAMEH8rzZUHFgYshMNYBE.
That fingerprint is an observation, not independent proof. The OpenBSD manual states that ssh-keyscan cannot verify the keys it collects. An attacker on the same network path could substitute another key. The manual says to compare the result through another channel or use it only when the network is trusted.[3]
ASCII Theater does not publish a fingerprint on its landing page. We found no independent value to compare. The honest state is observed, not verified.
Pin first, then press play.
We saved the observed key to a temporary file and connected with StrictHostKeyChecking=yes. A pseudo-terminal session received about 3 MB of ANSI output in eight seconds. We stopped the local client after that bounded check. This proves the service streamed terminal bytes through the key we had just observed. It does not prove who controls that key.
A stronger release path is short:
- The operator publishes the SSH fingerprint over HTTPS or DNSSEC-backed SSHFP.
- The viewer compares that value with the key offered by SSH.
- The viewer pins the matched key in a dedicated known-hosts file.
- The playback command keeps strict checking on.
The booth below teaches those claim levels. It does not fetch a key or decide that a fingerprint matches.