Ctrlk
PricingLog inSign up
For the complete documentation index, see llms.txt. This page is also available as Markdown.

How to migrate from MultiKey to SSH ID?

MultiKey is deprecated. MultiKey will no longer be available after September 15, 2026. Please migrate to SSH ID or other authentication method before then.

SSH ID is a passkey for SSH. It generates a device-bound key on each of your devices and keeps all public keys synced and available at a single URL: https://sshid.io/<your_handle>. Anyone can use this URL to fetch your public keys and provision them on a host. To learn more, see What is SSH ID.

Prerequisites

Before you start the migration, make sure every team member who needs access to your hosts has an SSH ID. To learn more, see Set up SSH ID.

Once a teammate sets up an SSH ID, they get a personal handle – https://sshid.io/<handle> – where all their public keys are available. You can use these handles to provision keys on your servers as described below.

We recommend each user to add at least two devices to their SSH ID, or keep a backup authentication method, to avoid losing access if a device is lost or unavailable.

Copy public keys from SSH ID

Termius provides two options to copy public keys from the teammates SSH IDs depending on how you want to provision them on your servers.

In the Settings -> Vaults, if you click the SSH ID button next to the vault, a context menu will appear listing all teammates and showing who has an SSH ID set up.

Click Copy passkeys to get all public keys in a plain text from every teammate's SSH ID at once. Use this when you want a quick bulk export.

Update the authorized_keys file on each host

Connect to the host that currently uses MultiKey and update its authorized_keys file.

Paste the copied keys directly into the server's ~/.ssh/authorized_keys file. Remove any key types your server does not require. For example, if your server only accepts ECDSA-SK, remove all other key type entries.

Set SSH ID as the authentication method

Once the ~/.ssh/authorized_keys file is updated, every user must switch the SSH ID authentication method on each host they need to access:

  1. Open Host Details for the host

  2. Scroll to the Credentials section and select Personal vault instead of Multikey

  3. Enter the username. If no username is set, your SSH ID handle is used as the default username

  4. Click + SSH ID, Key, Certificate, FIDO2

  5. Choose SSH ID as the authentication method

  6. Repeat this for every host you want to connect to

Verify the migration

  1. Connect to each host using SSH ID to confirm the connection works

  2. Check that no hosts remain configured with MultiKey

PreviousCan Termius be localized to other languages?NextTroubleshooting

Last updated

Was this helpful?