SSH, Actually 100% signal, 0% noise.

Setting Up a Non-Resident Key

procedure
depth 2/2 − deeper + surface

The setup for hardware-backed SSH where keys are derived on demand rather than stored: generate an ed25519-sk key, register the public key with the service, and take on the one obligation that comes with it—the blob file must be preserved.

Prerequisites:

  • A FIDO2-capable hardware key (YubiKey 5, YubiKey Bio, similar)
  • OpenSSH 8.2+ installed (ssh -V to check)
  • libfido2 installed (apt install libfido2-1 on Debian/Ubuntu)

1. Plug in hardware key

2. Generate non-resident SSH key

ssh-keygen -t ed25519-sk -f ~/.ssh/id_github_yk -C "github-hw"
  • Touch key when prompted
  • Set PIN if prompted
  • Creates blob file (required for authentication)

3. Add to GitHub/GitLab

Copy public key:

cat ~/.ssh/id_github_yk.pub
  • Go to GitHub Settings → SSH and GPG keys
  • Click "New SSH key"
  • Paste the contents
  • Save

4. Create SSH config

Edit ~/.ssh/config:

Host github.com
    IdentityFile ~/.ssh/id_github_yk
    IdentitiesOnly yes

5. Test it

ssh -T [email protected]
  • Touch key when prompted
  • Should see: "Hi username! You've successfully authenticated..."

What just happened:

  • Hardware key can derive unlimited private keys from blobs
  • Blob file must be preserved (back it up!)
  • Each service gets its own blob
  • No slot limit

Critical: back up your blob files! They're not secrets, but losing them means generating new keys.