SSH, Actually 100% signal, 0% noise.

Choosing an Approach

concept
depth 3/3 − deeper + surface

There are three viable setups: a disk-based key with a strong passphrase, a hardware-backed resident key, and a hardware-backed non-resident key. Which one you want depends on your situation—how many servers, whether you already own a hardware key, how much recovery capability you need—not on reaching for the maximum.

If you're trying to decide what to do, start here.

for ssh server access

Do you need to access servers?
│
├─ Yes, and I'm just getting started
│  → Use disk-based SSH keys with a strong passphrase
│
├─ Yes, and I want maximum security
│  → Use hardware-backed resident SSH keys
│
└─ Yes, and I manage dozens of servers
   → Use hardware-backed non-resident SSH keys

for git hosting (github, gitlab, etc.)

Do you need to authenticate to Git services?
│
├─ Yes, and I already have a hardware key
│  → Use hardware-backed non-resident SSH keys
│     (Unlimited keys, better security)
│
├─ Yes, but I don't have a hardware key
│  → Use disk-based SSH keys with a strong passphrase
│     (Still much stronger than passwords)
│
└─ Yes, and I want the absolute strongest security
   → Get a hardware key and use non-resident keys

quick recommendations by use case

Situation Recommended Approach Why
Personal laptop, accessing 1-2 servers Disk-based key with passphrase Simple, secure enough
Work laptop, accessing company infrastructure Hardware-backed resident keys Best security, survives laptop wipes
Developer using GitHub/GitLab daily Hardware-backed non-resident keys Unlimited keys, no passwords ever
System administrator, 20+ servers Hardware-backed resident keys Can't lose access, physical presence required
Learning SSH for the first time Disk-based key with passphrase Master the basics first

The pattern behind the trees:

  • Disk-based key with passphrase is the answer when you're learning or when the footprint is small—one laptop, one or two servers. Simple, secure enough, and still much stronger than passwords. Master the basics first; the hardware setups make more sense once the disk-based model is familiar.
  • Hardware-backed resident keys are the answer when losing access is the disaster you're designing against—company infrastructure, critical servers. Best security, survives laptop wipes, physical presence required. The cost: a scarce slot per key, and the obligation to keep a duplicate on a second device.
  • Hardware-backed non-resident keys are the answer when keys multiply—git hosting, dozens of servers and services. Unlimited keys, no passwords ever. The cost: you must preserve the blob files.

Notice what the git tree assumes: if you already own a hardware key, non-resident is simply better for git hosting—there is no tradeoff to weigh there. The genuinely close call is resident vs non-resident for server access, and that decision surface has its own node.