SSH, Actually 100% signal, 0% noise.

Recovery Planning

concept
depth 2/3 − deeper + surface

Every authentication setup should be built with its own failure in mind: keys get lost, disks die, passphrases and PINs get forgotten. Recovery planning means deciding—before anything breaks—how you will get back in. Security you can't recover from isn't strength; it's fragility with good cryptography.

The critical safety rules:

  1. Always have a recovery path

    • Second hardware key with duplicate keys, OR
    • Disk-based backup key stored securely, OR
    • Out-of-band access to servers
  2. For resident keys: two hardware keys, always

    • Primary key for daily use
    • Backup key stored safely with duplicate resident keys
  3. Blobs aren't secrets, but their loss is permanent

    • Back them up
    • They can't be reverse-engineered
    • But losing them means generating new keys
  4. Test your recovery process before you need it

    • Can you regenerate stubs?
    • Can you access servers with backup key?
    • Do you know your PIN?

For disk-based keys: always use strong passphrases (20+ characters), store the passphrase in a password manager, and back up private keys to encrypted storage. For hardware keys: store the backup key safely (not with the primary), test the backup regularly, and document your recovery process.