Guides
Keys and trust
Your key can't leave the device. Passwords stay in the Keychain. And Mucq won't connect to a server whose key has changed until you say so.
On this page
The device key
Mucq makes its key inside the device's Secure Enclave, the chip Apple built to hold keys. The private half can't be copied out of it: not by Mucq, not into a backup, not to another device. It's an ECDSA P-256 key, which OpenSSH accepts out of the box.
- One per device. Your Mac, your iPhone and your iPad each make their own. Add each one's public key to the server once.
- Made when needed, the first time you choose a key for a server, or with Create Device Key in Settings › SSH Keys.
- No prompt. Using the key asks for no Face ID or Touch ID.
- Gone with the device. A new or restored device makes a new key, and the server needs that new key once. On iPhone and iPad, deleting Mucq and installing it again starts fresh too: a new device key, and no stored passwords. On the Mac, Mucq keeps its key and passwords across a reinstall.
Settings › SSH Keys lists your keys. A key's menu has Copy Public Key and Copy Install Command for adding it to another server.
Your own keys
If a server already trusts a key of yours, import it: Import Key… on the Mac, or Import Key on iPhone and iPad, from Files or pasted. Mucq takes OpenSSH private keys of type Ed25519 or ECDSA. RSA keys can't be used.
Mucq asks for the key's passphrase once, at import, and never stores it. The key itself is kept in the Keychain on this device only. The file you imported it from is left as it was.
Passwords
A password goes in the Keychain when Remember password in Keychain is on, and stays on this device: it isn't synced to your other devices. The password field takes AutoFill, so a password manager can fill it.
Keys are the better choice. A server that accepts passwords is a server someone can guess at.
Host keys
Every SSH server has a host key of its own. It's how you know you reached your server and not someone pretending to be it.
The first time Mucq connects to a server, it shows the key's fingerprint and asks: Connect to devbox? Compare the fingerprint with what the server itself says, on the server or in your provider's console:
ssh-keygen -lf /etc/ssh/ssh_host_ed25519_key.pub
Choose Connect only when they match. Mucq remembers the key, one per host and port, and checks it on every connection.
When a host key changes
If the server ever presents a different key, Mucq doesn't connect, and doesn't offer to. It says devbox's host key has changed, with both fingerprints.
There are two reasons a key changes. Either the server was reinstalled or its keys were regenerated, which is harmless, or someone is intercepting the connection, which isn't. Only you can tell which. Host key changed shows how to check, and how to trust the new key once you're sure.
Nobody in between
Keys, passwords and host keys stay on your devices. Mucq talks to your servers and nothing else: there is no Mucq account and nobody between your device and your server.