Naming Keys
conceptWhen you create SSH keys, naming them clearly helps you (and others) understand their purpose. What matters: clarity (can you tell what the key is for?), intent (does the name reflect the key's purpose?), and scope (is it clear where this key should be used?). Names are for humans, not computers.
Common naming patterns:
Disk-based keys: ~/.ssh/id_purpose
id_github, id_homelab, id_work, id_personal_vps
Hardware-backed keys: ~/.ssh/purpose_yk
github_yk, gitlab_work_yk, production_servers_yk
The _yk suffix clearly indicates hardware-backed, prevents confusion with disk keys, and makes backup decisions easier. But any clear, consistent system works.
What doesn't matter: matching filenames across machines, keeping names secret, or following someone else's convention if you have your own system.
Why naming matters in practice:
- For blobs (non-resident hardware keys): you must preserve these files. Clear names help you identify what you're backing up—losing a blob means generating a new key.
- For human sanity: when you have 5+ keys, unclear names create confusion.
id_rsatells you nothing about purpose;github_personal_yktells you everything.
For public keys, the filename doesn't matter (they're deployed to servers)—the comment inside the public key matters more:
ssh-ed25519 AAAA... tyro@laptop-2024-github
A good comment format is username@device-year-purpose. It helps identify keys in server logs, makes authorized_keys management easier, and is useful when you have multiple keys.
The key insight: names are for humans, not computers. Make them useful to future-you.