Protecting SSH Keys with macOS Secure Enclave
Points and comments are a snapshot, not live.
Native macOS Secure Enclave SSH key setup works but suffers from an ugly Touch ID prompt.
The author describes setting up SSH keys backed by macOS's Secure Enclave using `sc_auth` and `ssh-keygen` with `SSH_SK_PROVIDER`. The private key is generated inside the Secure Enclave and cannot be exported. Each SSH operation requires Touch ID approval. The setup produces an unattractive Touch ID dialog reading "ctccardtoken needs to authenticate to continue." The author ultimately rejects the native approach for Secretive, a third-party app with a polished UI, but notes the native method is functional. Keys are device-bound and cannot be backed up; the author recommends maintaining multiple keys for redundancy.
What commenters are saying
Commenters generally favor Secretive for a better user experience. Several emphasize always keeping a backup key since Secure Enclave keys are unrecoverable if the device fails. One commenter warns about keychain consistency bugs, citing a WireGuard case where a system upgrade orphaned and deleted profiles stored in the keychain. Others note YubiKeys still occupy a USB port and lack biometric approval, while 1Password SSH offers portability but is software-based. A split appears between those who prefer hardware-backed keys (Secure Enclave, YubiKey) and those who accept software vaults for convenience.