• Sources: primary, discussion
  • Summary: Alex Haydock describes replacing all on-disk SSH keys with ed25519-sk keys on YubiKeys, TPM-sealed keys through ssh-tpm-agent, and non-exportable Secure Enclave keys created with sc_auth on macOS. He notes that TPM keys still keep an encrypted key file on disk and that no-touch-required keys need a matching authorized_keys option. The thread reached 204 points and 106 comments.
  • Why it matters: Hardware-bound SSH keys stop a compromised laptop or agent from copying a key that also signs commits or reaches production hosts.
  • Comments: Commenters explain that resident keys can be recovered from the YubiKey with ssh-keygen -K while non-resident keys need the handle file too. One reports GitHub accepts touch-required resident keys while Bitbucket rejects FIDO keys, others use the OpenPGP or PIV slot to cache touches, and several warn to enroll multiple keys after a YubiKey failed or melted.