GoTerm
All guides

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
  1. The checks on the way in
  2. How a secret is stored
  3. When a secret is opened
  4. Turn on two-factor
  5. Keep your recovery codes
  6. Signing in with a code
  7. The workspace’s rule
  8. A new device
  9. Where sign-ins come from
  10. What you can do
  11. Good to know

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.

Someone signing ina browser or the appAllowed addressesaddresses you choosePrivate accessyour own devices, over WireGuardPassword and two-factora code, where two-factor is onA confirmed devicea new one waits until someoneconfirms itRole or grantonly the hosts they may reachRead-only at thegatewaya viewer’s typing neverreaches the serverYour servers
Six checks, outermost first: allowed addresses and Private access, dashed because a workspace switches them on, then the password and code, a confirmed device, the role or grant, and read-only at the gateway.
  • 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.

Your secreta password or a private keySealedAES-256-GCM, its own keyThat key sealedby a master key kept apartStoredonly sealed data
Your secret is sealed with AES-256-GCM under a key of its own; that key is sealed by a master key kept apart from the database; only the sealed results are stored.
  • 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.

to connectusedYour sealed keyin the VaultThe gatewayopens it in memoryYour serversigns in with itLogs and errorsneverYour browserneverPeople you share withnever
When you connect, the gateway opens your key in memory and signs in to the server with it. The key never goes to logs or error messages, to your browser, or to the people you share with.
  • 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.

  1. Open your name at the bottom of the sidebar, then Two-factor sign-in.
  2. Scan the QR code with an authenticator app, or type the key it shows into the app.
  3. Type the code the app shows, then choose Turn on.

Keep your recovery codes

  1. Right after, GoTerm shows ten recovery codes, once. Each one signs you in once without your phone.
  2. Choose Copy the codes and keep them somewhere safe. Tick I've saved them somewhere safe, then choose Done.
  3. 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.

You → GoTermEmail and passwordGoTerm → YouAsks for a codeAuthenticator app → YouShows a 6-digit codeYou → GoTermTypes the codeGoTermChecks the code, then the deviceGoTerm → YouSigned in
After the password, GoTerm asks for the code your authenticator app shows, then checks the device.
  • 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.

  1. Switch on Require it of everyone, and members and contractors set it up at their next sign-in.
  2. 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.
  3. 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.

  1. The waiting screen names the device, the address it signs in from, and its ID, such as 234D-1571.
  2. 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.
  3. Check the ID is the same on both screens before you confirm. The waiting screen goes on by itself.

Where sign-ins come from

  1. Open Vault, then Devices: each device you use, where it was last seen, and when.
  2. 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.
  3. 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.

Ask an engineer
  • Getting started

    Try the demo, add your first host and open a terminal.
  • Desktop app

    Install it on Windows, dial from your own computer, or use it free.
  • Hosts and jump hosts

    Quick connect, groups, and private servers through a bastion.
  • Sessions and sharing

    Keep sessions running, come back to them, and share them live.
  • Files

    Move files beside your terminal, or between hosts.
  • Web tabs and tunnels

    Open private pages and forward ports through a host.
  • Snippets

    Save commands once, and run them on one host or ten.
  • Monitors

    Check sites and ports, and get told when they go down.
  • Teams and roles

    People, teams, roles, host groups and each team’s activity.
  • Access and contractors

    Give a host for a few hours, and see what changed after.
  • Audit log and recordings

    Who did what, from where, and what their screen showed.
  • Running a workspace

    Your address and region, colours, settings and moves.
  • The Vault and your keys

    Save, share and replace passwords and private keys.
  • Allowed addresses

    Open your workspace only from your office’s network.
  • Private access

    Open your workspace only to your team’s own devices.