BrainHack vs Bastion SSH

BrainHack is an interpreter app for B*******k. The B*******k programming language is an esoteric programming language noted for its extreme minimalism. It is a Turing tarpit, designed to challenge and amuse programmers, and was not made to be suitable for practical use. It was created in 1993 by Urban Muller. Commands: > increment the data pointer (to point to the next cell to the right). < decrement the data pointer (to point to the next cell to the left). + increment (increase by one) the byte at the data pointer. - decrement (decrease by one) the byte at the data pointer. . output a character, the ASCII value of which being the byte at the data pointer. , accept one byte of input, storing its value in the byte at the data pointer. [ if the byte at the data pointer is zero, then instead of moving the instruction pointer forward to the next command, jump it forward to the command after the matching ] command. ] if the byte at the data pointer is nonzero, then instead of moving the instruction pointer forward to the next command, jump it back to the command after the matching [ command.

Bastion SSH is an SSH and SFTP client built for the way real infrastructure is laid out: not one server you can dial directly, but a bastion, then a machine behind it, then the box you actually wanted. Chains, not just connections: - Reach a host through any number of jump hosts, the way `ssh -J` does - Every hop is a real SSH session, so every machine in the chain is authenticated and its host key checked — not just the first one - Routes are named by where they go: "office-A → mac-mini". Past the first hop addresses stop being unique — a reverse tunnel puts every machine on its jump's localhost — so the path is what tells two otherwise identical routes apart - Add a new jump host inline while you set one up, at any depth - When a chain fails it names the hop, the stage it got to, and the jump it came through, so you can tell a dead tunnel from a machine that is switched off Know what will happen before you connect: - Open a route and see it hop by hop, with what each step will use: a stored key, a stored password, or a prompt - It answers the question up front — "1 of 3 hops will ask for credentials" - Install a public key onto any hop from the same screen Keys that stay on the device: - Generate a key on your phone: the private half goes straight into the system key store and never exists as a file, and only the public key ever leaves - Import the key you already own: OpenSSH format (what ssh-keygen writes by default) or PEM, encrypted or not, with no conversion step - "This device" lists every key with its type, fingerprint, which hosts use it, and whether it was generated here or imported - Use one key across several hosts, and delete a key only after being told how many hosts depend on it Host keys you can verify: - Fingerprints are the OpenSSH SHA256 form, exactly what `ssh-keygen -lf` prints, so you can compare them with the server instead of taking them on trust - A changed host key asks you, every time - Records are kept per route, so two machines that both answer on their bastion's localhost are never confused Multi-session terminal: - Session tabs that live independently — switch, close or retry one without disturbing the rest - xterm-compatible terminal with selection, copy and paste, and resize - Quick keys for the commands and control sequences you keep reaching for - Per-host keep-alive, and reconnection that backs off instead of hammering the server Files: - Browse, download, upload, rename and delete over SFTP - Downloads keep running when you leave the screen, with progress and cancel - Save through the system file picker, or keep them in the app Credentials, on your terms: - A hop's password can be kept in the device key store, per host, and using it needs the device's own check — your face, a fingerprint, or your passcode - One check covers a few minutes of use, then it locks itself again — a found phone is not an open door - Each stored password says which protection it has - A stored password the server rejects is dropped and you are asked again, instead of failing the same way on every attempt - Review and revoke everything that is stored from one screen Yours, and only on your device: - Hosts, keys and known-host records stay on the device. No account, no sync, nothing to sign up for - Private keys live only in the system key store, never as plaintext files - Privacy policy and terms are available from within the app Great for: - Anyone whose servers sit behind a bastion or a reverse tunnel - Sysadmins and developers checking on machines away from a desk - Keeping several sessions open at once — logs in one tab, work in another - Setting up key authentication from a phone, without moving a private key around Open the route. See the hops. Connect.