Lion Cipher Lab

Scale SSH beyond keys with a certificate authority

Why it matters

Raw SSH keys work beautifully for one person and a handful of servers, and they fall apart at scale: every machine keeps its own authorized_keys file, so onboarding, offboarding, and key rotation mean touching every box by hand, and it is genuinely hard to answer 'who can log into what, and should they still?' A certificate authority replaces that sprawl with one trust anchor. The server trusts the CA, the CA signs a certificate that says who you are, which accounts you may use, and — critically — for how long. Short-lived certificates mean access expires on its own instead of lingering in a…

What you'll learn

Steps in this lab

  1. The problem keys leave behind: authorized_keys everywhere
  2. What an SSH certificate authority actually is
  3. Create your CA key pair (and guard it like gold)
  4. Sign a short-lived USER certificate
  5. Teach the server to trust the CA (TrustedUserCAKeys)
  6. Log in with the certificate and watch it expire
  7. Sign a HOST certificate to end the trust-on-first-use prompt
  8. Why short-lived certificates beat long-lived keys

Open the full interactive lab →