Use an SSH key, and make one with PuTTYgen

Why a key is safer and easier than a password, how to make one with PuTTYgen, and how to get it onto your VMs.

Updated 6 November 2026

Use an SSH key if you possibly can. A VM's SSH port is open to the whole internet, and automated bots try passwords on it all day long. They'd never guess a key.

Why a key beats a password

  • It can't be guessed. A key is far longer than any password, and your VM doesn't need password login switched on at all.
  • It never leaves your computer. The server only ever gets proof that you hold the key, not the key itself. A compromised server can't steal it.
  • It's quicker. Saved in PuTTY, a key logs you in with a double-click.
  • It works everywhere. Add one key to your account and any VM you build can use it, as can rescue mode.
  • It's how Cloud VMs are built. Most have no lasting password, so a key is the normal way in.

A key comes in two halves. The private key stays on your computer and is treated like a password. The public key can go anywhere, and it's what you give the panel. Never give anyone your private key, including us.

Make a key with PuTTYgen

PuTTYgen comes with PuTTY. Search for it in the Start menu.

  1. Under Parameters, choose EdDSA, and check it says Ed25519 (255 bits). If your version doesn't offer it, update PuTTY, or choose RSA with at least 4096 bits.
  2. Press Generate and move your mouse around the empty area until the bar fills up.
  3. Change Key comment to something you'll recognise, such as my-desktop.
  4. Type a Key passphrase, and again under Confirm passphrase. This protects the key if someone gets hold of your computer. You can leave it empty, but it's worth having.
  5. Press Save private key and keep the .ppk file somewhere safe, with a backup. If you lose it, there's no way to get it back.
  6. Leave the window open. You need the public key next.

Add it to your account

  1. Select everything in the box at the top of PuTTYgen, Public key for pasting into OpenSSH authorized_keys file, and copy it. It's one long line starting ssh-ed25519.
  2. On the panel, open your account's SSH keys.
  3. Give it a name, paste the key in, and save.

Copy from the box. Don't use the Save public key button, as that makes a file in a different format that the panel won't accept. If you've lost the box, open your .ppk in PuTTYgen with Load and it comes straight back.

The panel takes Ed25519, ECDSA, and RSA keys of at least 2048 bits, but not DSA.

Put it on a new VM

Tick your key under SSH keys when you build the VM. That's all there is to it. Then connect with PuTTY, choosing the .ppk file under Connection > SSH > Auth > Credentials.

Add your key to a VM that already exists

Keys on your account are copied to a VM when it's built. Adding one later doesn't reach VMs you already have, so put it there yourself.

  1. Log in another way. On the Info tab, use Turn on SSH password login, or another key that already works.
  2. Paste this in, using your own public key between the quotes:
mkdir -p ~/.ssh && chmod 700 ~/.ssh
echo 'ssh-ed25519 AAAA...your key... my-desktop' >> ~/.ssh/authorized_keys
chmod 600 ~/.ssh/authorized_keys
  1. Open a second PuTTY window and check the key logs you in, before you close the first one.
  2. On the Info tab, press Turn it off now.

Locked out with no way in at all? Rescue mode can add a key.

Good habits

  • One key per computer, and one per person. If a laptop goes missing, you can remove that one key without changing the others. Project members should each use their own.
  • Removing a key from your account doesn't remove it from your VMs. To remove access, delete its line from ~/.ssh/authorized_keys on each VM.
  • Pageant comes with PuTTY and remembers your key once unlocked, so you only type your passphrase once per session.
  • Using a Mac or Linux? Run ssh-keygen -t ed25519, then paste the contents of ~/.ssh/id_ed25519.pub into the panel.