Protect SSH Keys with macOS Secure Enclave: Complete Setup Guide

What Causes This Issue

Many Mac users attempting to protect SSH keys with the Secure Enclave encounter failures during key generation, authentication prompts that never appear, or keys that work intermittently. The root cause typically falls into three categories: hardware compatibility gaps, Keychain access misconfiguration, or SSH agent integration conflicts.

The Secure Enclave is a dedicated hardware security module isolated from the main processor. It generates and stores private key material that never leaves the chip. When you create an SSH key backed by the Secure Enclave, the private key cannot be extracted — only the public key is exported. Authentication requires biometric authentication via Touch ID or Face ID, or your device passcode.

Users in the Apple Support Community report that macOS version mismatches, missing developer tools, and incorrect SSH agent configuration cause most failures. Intel-based Macs with T2 chips support this feature, as do all Apple Silicon Macs. Older hardware lacks the necessary secure element entirely.

Step-by-Step Fixes

1. Verify hardware compatibility. Click the Apple menu > About This Mac. Confirm your Mac has Apple Silicon (M1/M2/M3 series) or an Intel Mac with T2 Security Chip (2018 or later). Without this, Secure Enclave SSH keys are impossible.
2. Update macOS. Open System Settings > General > Software Update. Install the latest version. Secure Enclave SSH support arrived in macOS Ventura 13.3 and improves in Sonoma and Sequoia.
3. Install Command Line Tools. Run xcode-select --install in Terminal. Accept the license. These tools provide the ssh-keygen binary with Secure Enclave support.
4. Generate the Secure Enclave backed key. Execute: ssh-keygen -t ecdsa-sk -f ~/.ssh/id_ecdsa_sk. The -sk suffix denotes security key — Apple’s implementation uses the Secure Enclave. When prompted, authenticate with Touch ID, Face ID, or your password.
5. Verify key creation. Run ls -la ~/.ssh/id_ecdsa_sk*. You should see the private key file (no extension) and .pub public key. The private key file is a stub — actual key material remains in the Secure Enclave.
6. Add public key to target servers. Copy the .pub content to ~/.ssh/authorized_keys on each remote host. Use ssh-copy-id user@host or manually append the line.
7. Test authentication. Run ssh user@host. A biometric prompt should appear. Authenticate to complete the connection. If no prompt appears, proceed to Additional Solutions.
8. Configure SSH agent for persistence. Edit ~/.ssh/config and add: Host *
AddKeysToAgent yes
UseKeychain yes
IdentityFile ~/.ssh/id_ecdsa_sk. This ensures the key stub loads into the agent after reboot.

Additional Solutions

Reset Keychain access for SSH. Open Keychain Access (Applications > Utilities). Search for “ssh” or “Secure Enclave.” Delete any entries related to your SSH key. Re-run the key generation steps. Corrupted Keychain entries frequently block biometric prompts.

Enable SSH agent launch daemon. Create ~/Library/LaunchAgents/com.user.ssh-agent.plist with:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
  <key>Label</key><string>com.user.ssh-agent</string>
  <key>ProgramArguments</key>
  <array>
    <string>/usr/bin/ssh-agent</string>
    <string>-s</string>
  </array>
  <key>RunAtLoad</key><true/>
  <key>KeepAlive</key><true/>
</dict>
</plist>

Load it: launchctl load ~/Library/LaunchAgents/com.user.ssh-agent.plist. This maintains the agent across sessions.

Disable conflicting SSH agents. If you use 1Password, Bitwarden, or another password manager with SSH agent integration, disable their SSH agent feature. Multiple agents cause race conditions where the wrong agent handles the key.

Use ED25519-SK as alternative. If ECDSA-SK fails, try ssh-keygen -t ed25519-sk -f ~/.ssh/id_ed25519_sk. Some users report better reliability with Ed25519. The process is identical.

Clear SSH known hosts for problematic servers. Run ssh-keygen -R hostname to remove stale entries. Then reconnect and accept the new host key.

Check Secure Enclave availability. Run system_profiler SPiBridgeDataType on Apple Silicon or system_profiler SPHardwareDataType | grep -i secure on Intel. Verify “Secure Enclave” appears with “Enabled” status.

When to Contact Apple Support

Contact Apple Support if:

• Your Mac reports Secure Enclave as disabled or unavailable in System Information despite supported hardware
• Biometric authentication fails system-wide (not just for SSH)
• Key generation returns “security key enrollment failed” or “operation not supported” after all troubleshooting steps
• macOS Recovery shows Secure Enclave errors during diagnostics
• You suspect hardware damage to the Secure Enclave processor

Bring your Mac to an Apple Store or Authorized Service Provider. They can run AST2 (Apple Service Toolkit) diagnostics that validate Secure Enclave functionality beyond user-visible tools.

FAQ

Can I use Secure Enclave SSH keys on multiple Macs? No. Each Secure Enclave is unique to its device. Generate a separate key pair on each Mac and add all public keys to your servers’ authorized_keys.

Do Secure Enclave keys work with GitHub, GitLab, and Bitbucket? Yes. Add the public key (id_ecdsa_sk.pub or id_ed25519_sk.pub) to your account’s SSH keys section. Git operations will trigger biometric prompts.

What happens if I erase my Mac or replace the logic board? The Secure Enclave keys are destroyed. You must generate new key pairs and update all remote authorized_keys files. Back up only the public keys.

Can I use these keys with sudo or local sudo authentication? No. macOS sudo does not currently support Secure Enclave keys for local authentication. Use Touch ID for sudo via /etc/pam.d/sudo configuration separately.

Why does my key work in Terminal but not in VS Code or other editors? GUI apps launch non-interactive shells that may not inherit the SSH agent environment. Ensure your shell config (~/.zprofile, ~/.bash_profile) starts the agent and adds keys. Restart the editor after changes.

Is there a way to require biometric authentication for every single SSH operation? Yes. The Secure Enclave enforces this by default. Each signing operation requires a fresh biometric check. There is no “remember for session” option — this is a security feature, not a bug.