Keys and security
Safe sign-ins, sealed secrets
Every sign-in passes the same checks, in order: where it comes from, the password and a code where two-factor is on, a confirmed device, then what the person may reach. Saved passwords and keys are sealed, and opened only to connect.
Updated
On this page
The checks on the way in
Before anyone reaches a server, GoTerm checks where they come from, who they are, their device and what they may do. The first two checks are switches a workspace turns on.
- In a browser, your sign-in is kept in a cookie the page’s scripts can’t read.
- Your workspace talks to GoTerm directly over TLS. Terminal traffic never passes through a CDN.
How a secret is stored
Each password and key is sealed with a key of its own. That key is sealed again by a master key kept apart from the database, so a copy of the database alone opens nothing.
- A new key every time a secret is saved again.
- Master keys rotate without opening anyone’s secrets.
- A sealed secret is tied to its own workspace and record: copied anywhere else, it won’t open.
When a secret is opened
The gateway signs in to your server for you, so it opens your key at that moment, in memory, and lets it go once it has signed in.
- That’s why GoTerm never calls itself end-to-end encrypted: the gateway uses your key, for a moment.
- Once saved, a password or key isn’t shown in the browser again. A key GoTerm makes for you can be downloaded once, as it’s made.
- Your personal keys go only to desktops you confirmed, sealed for each one. A team’s never leave GoTerm.
Turn on two-factor
A code from an authenticator app on your phone, as well as your password. Owners and admins must have it.
- Open your name at the bottom of the sidebar, then Two-factor sign-in.
- Scan the QR code with an authenticator app, or type the key it shows into the app.
- Type the code the app shows, then choose Turn on.
Keep your recovery codes
- Right after, GoTerm shows ten recovery codes, once. Each one signs you in once without your phone.
- Choose Copy the codes and keep them somewhere safe. Tick I've saved them somewhere safe, then choose Done.
- Lost your phone? At sign-in, choose Lost your phone? Use a recovery code.
Tip: Lost the codes, or used most of them? New recovery codes, under Two-factor sign-in, makes a new set and ends the old one.
Signing in with a code
The code comes right after the password, before anything else. Someone with only your password gets no further, and can’t set off a device confirmation email.
- Each code works once. Five wrong codes end the try, and ten in 15 minutes pause code checks and email you.
- Lost your phone and your codes? The owner resets it, or an admin for a member or a contractor, with a code from their own app.
The workspace’s rule
Owners and admins set it under Admin, then Security.
- Switch on Require it of everyone, and members and contractors set it up at their next sign-in.
- Under Ask for the code, choose how often: Every sign-in, once a day, a week or 30 days on each device, or Only on a new device.
- Whatever you choose, a device’s first sign-in always asks.
A new device
A browser or computer you haven’t used before waits until you confirm it, even with the right password and code.
- The waiting screen names the device, the address it signs in from, and its ID, such as 234D-1571.
- Open the link we email you, or confirm it from Vault, then Devices, on a device you already use. An admin can confirm it too.
- Check the ID is the same on both screens before you confirm. The waiting screen goes on by itself.
Where sign-ins come from
- Open Vault, then Devices: each device you use, where it was last seen, and when.
- Where GoTerm can place an address, the city and country show beside it. A sign-in from an anonymous network, such as Tor, is marked so, where GoTerm can tell.
- A device you don’t know? On its … menu, choose Turn it down while it waits, or Sign out and remove once confirmed.
What you can do
- Turn on two-factor, even where your workspace doesn’t ask for it.
- Look at Vault, then Devices, now and then, and remove what you don’t know.
- When a server is rebuilt, forget its old key under Known hosts, then connect again.
- Share a session read-only unless someone needs to type: the gateway enforces it.
- Replace a key that may have leaked: every host that uses it signs in with the new one from its next connection.
Good to know
- The gateway opens SSH connections to your servers and nothing else, with rate limits and a record of every refused connection.
- Host keys are pinned on the first connect: a changed key stops the connection.
- What a session printed is kept in the gateway’s memory to replay, never on disk. A recording is stored sealed, like a saved key.
- Your two-factor key is sealed like the Vault’s items, and recovery codes are kept only as hashes.
Didn’t find your answer?
Write to us, and an engineer who builds GoTerm will reply.




