SSH Keys

Open the SSH Keys page in my.cubepath.com to manage SSH keys for secure server access.

Your key library

This page is your account-wide SSH key library. Keys saved here are stored once and reused across deployments: pick them when you deploy a new server, or attach them to an existing VPS or dedicated server. Each key shows its Name, Type, Fingerprint and who created it.

Note

Only public keys are stored here. Your private key never leaves your computer, and nothing on this page could reveal it.

Add a key

Click SSH Key and fill in:

• Key Name — a label to recognize the key later (e.g. Laptop – Ana).
• Public Key — the full public key, for example ssh-ed25519 AAAAC3NzaC1lZDI1NTE5....

Accepted types are ED25519, RSA and ECDSA. If you don't have a key yet, the dialog includes a How to Generate guide with the commands for macOS, Linux and Windows.

Tip

Name keys after the person and device, not the server. A key called Laptop – Ana tells you what to revoke when Ana's laptop is stolen; one called web-server tells you nothing.

Note

Pasting a public key that already exists in your library shows This SSH key already exists — you can't add a duplicate.

Edit or delete

Edit renames a key; the public key itself can't be changed, only its name. Delete removes it from your library after a confirmation. You can also Copy Key or Copy Fingerprint straight from the table.

When keys take effect

Important

A key only grants access where it's actually installed. Adding it to this library alone does not install it on any existing server.

A key reaches a server at one of three moments:

• You select it at deploy time.
• You attach it on the server's SSH Keys tab and then reinstall the operating system.
• You add it to ~/.ssh/authorized_keys yourself over SSH.

The same applies in reverse, and this is the part that matters for security: deleting a key here does not remove it from running servers. To actually revoke access, remove the key from ~/.ssh/authorized_keys on every machine it was installed on.

A workable convention

• One key per person per device. Shared keys can't be revoked individually.
• Prefer ED25519. It's short, fast and current; RSA is fine if you need compatibility with something old.
• Audit the list when someone leaves. The library is the inventory — the servers are where you enforce it.