As cool as this is, this does limit the functionality of your keys, because not everything can access the secure enclave in the way it wants to - and as others point out, this is a one-way street and locks your mac hardware into the flow.
I went with this system for some months but it ultimately broke my workflow. I switched to a system of my own devising, in which my local security key decrypts the SSH keys I require.
If you do this, have at least one backup key (if need be on paper) or a guaranteed alternate path into the hosts you depend on this key to access. Because if the secure enclave is as good as we're told, if you lose access to ->THIS<- secure enclave, its game over for the keys.
Secure enclave protecting Keychain, the keychain is backed up. Not the contents of the enclave.
Too many failed access attempts? poof the key is gone. Could be as low as 10.
(happy to be corrected. This is what I gather from a quick read-around. I was a bit surprised the site didn't seem to discuss this)
As cool as this is, this does limit the functionality of your keys, because not everything can access the secure enclave in the way it wants to - and as others point out, this is a one-way street and locks your mac hardware into the flow.
I went with this system for some months but it ultimately broke my workflow. I switched to a system of my own devising, in which my local security key decrypts the SSH keys I require.
> No key files (like ~/.ssh/id_ed25519.pub and friends) littering the file system; and there’s no risk of mistakenly deleting them either.
Or backing them up, or copying them to your new computer. You're just one spilled coffee cup away from losing the key.
Yes, this only works if you can register more than 1 ssh keys on the services you want.
If you do this, have at least one backup key (if need be on paper) or a guaranteed alternate path into the hosts you depend on this key to access. Because if the secure enclave is as good as we're told, if you lose access to ->THIS<- secure enclave, its game over for the keys.
Secure enclave protecting Keychain, the keychain is backed up. Not the contents of the enclave.
Too many failed access attempts? poof the key is gone. Could be as low as 10.
(happy to be corrected. This is what I gather from a quick read-around. I was a bit surprised the site didn't seem to discuss this)
happy 1Password user since years, provides this too and you'll have you ssh keys in the 1P keychain (yes, not open source, I know - only flaw imho)
That would make it extractable and syncable to other hosts. That's fine if that's what you want but it's an important distinction.
yes, that's exactly what I want :) (and the private key is only living inside 1Password and isn't extractable from there)
https://www.1password.dev/ssh/manage-keys#export-an-ssh-key
You’re mistaken. 1Password syncs keys. Therefore, they’re extractable.