Move to cloud

The servers you reach from your Mac with ssh can open from tTerm Web, your phone or any computer you sign in on. Move to cloud in tTerm for Mac takes them to your account, each the way you choose for it. Nothing moves until you press Move.

Where it is

Sign in to tTerm for Mac, open the account at the bottom of the sidebar and choose Move to cloud, right above Sign out. ⌘K finds it too.

What it finds

Servers on this Mac come from ~/.ssh/config, known_hosts and the ssh commands you ran in tTerm’s terminals on this Mac. For each one, ssh -G gives the address, port, user, keys and bastion that ssh itself would use; the user and port you typed, as in ssh root@host or -p 2222, take the place of the config’s. The Mac connects to none of the servers for this.

All the servers are ticked, except a git host such as github.com (A git host: no terminal to open), a server that is In tTerm already, one that only known_hosts knows, and one you chose Don’t ask for … on the strip. Then tTerm Web checks, from the cloud, whether it can connect to each server’s SSH port, or to its bastion’s.

Under the servers, Keys in ~/.ssh lists your private keys. Only the ticked ones go to your vault. A key is ticked by itself when a ticked server opens with it by My key.

Three ways in

Each server has a choice of its own:

My key – the key goes to your vault, encrypted on this Mac, and the server stays as it is. tTerm Web signs in from the cloud, and a device of yours with the vault open signs the login: a browser where you opened the vault, or this Mac. For a server tTerm Web reaches, with a key in ~/.ssh that can move. More in Your vault of SSH keys.
tTerm’s pass – this Mac signs in once and adds tTerm’s own line to ~/.ssh/authorized_keys of the user it signs in as; your key stays here. From then on tTerm signs in as that user with a certificate that lives two minutes, as on a server connected with one command, and needs no vault. On the strip after ssh, this way is Let tTerm in.
Through this Mac – nothing moves: tTerm asks this Mac to run ssh to the server, while the Mac is on. For a server behind a VPN or on a private network, which tTerm Web cannot reach, and for one whose key cannot leave this Mac. Its terminal runs in the classic mode: every key goes straight to ssh on the Mac, with no blocks and no question before a dangerous command.

tTerm picks for each server: My key where its key can move, Through this Mac where tTerm Web does not reach the server or its key cannot leave, tTerm’s pass otherwise. A server tTerm Web does not reach has only Through this Mac. A server behind a bastion that the cloud reaches opens through that bastion.

When you press Move

The button counts the ticked servers: Move 3 servers.

My key needs your vault. The first time, press Make my vault with Touch ID and keep the recovery code. A locked vault asks for Touch ID or your Mac’s password, or, on a Mac with no lock of it yet, the recovery code once.
For a key with a passphrase, tTerm asks for it once. The passphrase stays on this Mac.
With My key, this Mac first signs in to the server with that key alone; only then the key goes to your vault, once for all its servers. With tTerm’s pass, this Mac signs in to add the line, and tTerm signs in once with its certificate to check it.
My key and tTerm’s pass need the server’s host key in known_hosts: connect to a new server from this Mac once first.

Nothing is saved for a server that fails. A key that went to the vault only for servers that failed comes out of it again, and a line tTerm added on such a server comes off.

After the move

The result says how many servers are now in tTerm, all in Personal: 2 of 3 servers are in tTerm. Each line says how its server opens: Opens with your key, Opens with tTerm’s pass or Through this Mac, while it is on. Beside it, Open a terminal opens one there. A server that failed says why, with Try again and Change: Change goes back to the list with only that server ticked. At the bottom: the keys now in your vault, or No key moved: your keys stay on this Mac.

In the sidebar, a server that opens with your key has a key after its name, and one that goes through your Mac says via Mac.

The strip after ssh

When ssh ends without an error in a terminal of this Mac, a strip may come up under its block: droplet: open it from anywhere, with the address and your key.

Save my key – the same as My key, where the key can move.
Let tTerm in – the same as tTerm’s pass.
Not now, or Don’t ask for droplet.

For a server tTerm Web does not reach, the strip offers Open it through this Mac instead. It comes once for each server, and never for a git host or a server already in tTerm. A server saved from the strip goes to Personal too.