Choosing an Approach
conceptThere 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 |