Hardware Keys for SSH
conceptHardware SSH keys don't change the cryptography. They change where authentication memory lives. Everything else follows from that.
Why hardware-backed SSH feels strange: with web auth, you visit a site, the browser handles everything, the key just "works." With SSH, there are files in ~/.ssh/, some are called "blobs," others "stubs," terms like "resident" and "non-resident" appear, and it's not clear what goes where or why.
The confusion comes from one shift:
Hardware keys change where authentication state lives.
Traditional SSH puts all state on disk—the private key file is the full secret, copyable, losable. Hardware-backed SSH splits state between your computer and the hardware key. That split is the entire design.
Mechanically, modern SSH simply reuses FIDO2 hardware keys as signing devices—the ed25519-sk key type uses FIDO2 as a signing oracle. SSH predates all of the modern web-auth machinery: it already uses key-pair cryptography, already knows the username, and does not need discovery. This is why SSH keys, WebAuthn, and passkeys feel related—they are.