SSH is ubiquitous. It’s the de-facto solution for remote administration of *nix systems. But SSH has some pretty gnarly issues when it comes to usability, operability, and security.
You’re probably familiar with these issues:
- SSH user experience is terrible. SSH user on-boarding is slow and manual. Connecting to new hosts produces confusing security warnings. You’re left with weird new credentials to manage with little guidance on how to do so.
- Operating SSH at scale is a disaster. Key approval & distribution is a silly waste of time. Host names can’t be reused. Homegrown tools scatter key material across your fleet that must be cleaned up later to off-board users.
- SSH encourages bad security practices. Rekeying is hard, so it’s not done. Users are exposed to key material and encouraged to reuse keys across devices. Keys are trusted permanently, so mistakes are fail-open.
The good news is this is all easy to fix.
None of these issues are actually inherent to SSH. They’re actually problems with SSH public key authentication. The solution is to switch to certificate authentication.
SSH certificate authentication makes SSH easier to use, easier to operate, and more secure.
At smallstep, certificates are kind of our jam. We build open source software that lets you run your own private certificate authority and manage X.509 (TLS/HTTPS) certificates.
SSH certificates have been on our radar for a while. From our perspective they’re all pros, no cons. But no one uses them. Why not? We’ve asked hundreds of people that question. Here’s what we found out:
- People do use SSH certificates. In fact, pretty much everyone operating at scale that knows what they’re doing does (Facebook, Uber, Google, Netflix, Intercom, Lyft, etc), but…
- Certificates and public key infrastructure (PKI) are hard to grok. People don’t immediately understand the benefits.
- There’s a (small) tooling gap that exacerbates this knowledge gap. It’s not hard to fill, but people are wary to do so themselves without a deeper understanding of PKI concepts.
- More than anything, SSH certificates haven’t gotten the press they deserve. Most people we asked hadn’t heard of them at all.
We’re convinced that SSH certificates are the right way to do SSH. They’re not that hard to understand, and it’s well worth the effort. SSH certificates deserve more press, and broader use.
Public key authentication
Most SSH deployments use public key authentication, which uses asymmetric (public key) cryptography with a public / private key pair generated for each user & host to authenticate.
The magic of asymmetric cryptography is the special correspondence between a public and private key. You can sign data with your private key and someone else can verify your signature with the corresponding public key. Like a hash, it’s computationally infeasible to forge a signature. Thus, if you can verify a signature, and you know who owns the private key, you know who generated the signature.
Simple authentication can be implemented by challenging someone to sign a big random number. If I open a socket to you and send a random number, and you respond with a valid signature over that number, I must be talking to you.
This is an oversimplification, but it’s more or less how SSH public key authentication works. Certificate authentication works the same way, but with an important twist that we’ll get to in a moment.
To SSH to a host using public key authentication the host needs to know your public key. By default, your public key must be added to
~/.ssh/authorized_keys. Maintaining this file for every user across a fleet is operationally challenging and error prone.
SSH user onboarding with public key authentication usually starts with some baroque incantation of
ssh-keygen, hopefully pulled from a runbook, but more likely cribbed from stack overflow. Next you’ll be asked to submit your public key for approval and distribution. This process is typically manual and opaque. You might be asked to email an administrator or open a JIRA ticket. Then you wait. While you’re doing that, some poor operator gets interrupted and told to add your key to a manifest in some repo and trigger a deploy. Once that’s done you can SSH. Since key bindings are permanent, your SSH access will continue in perpetuity until someone reverses this process.
Certificate authentication eliminates key approval and distribution. Instead of scattering public keys across static files, you bind a public key to a name with a certificate. A certificate is just a data structure that includes a public key, name, and ancillary data like an expiration date and permissions. The data structure is signed by a certificate authority (CA).
$ ssh-keygen -L -f id_ecdsa-cert.pub id_ecdsa-cert.pub: Type: firstname.lastname@example.org user certificate Public key: ECDSA-CERT SHA256:O6M6oIjDm5gPm1/aTY619BgC3KSpS4c3aHVWxYh/uGQ Signing CA: ECDSA SHA256:EY2EXJGoPv2LA6yEbjH+sf9JjG9Rd45FH1Wt/6H1k7Y Key ID: "email@example.com" Serial: 4309995459650363134 Valid: from 2019-09-11T14:50:01 to 2019-09-11T18:50:01 Principals: mike Critical Options: (none) Extensions: permit-X11-forwarding permit-agent-forwarding permit-port-forwarding permit-pty permit-user-rc
To enable certificate authentication simply configure clients and hosts to verify certificates using your CA’s public key (i.e., trust certificates issued by your CA).
On each host, edit
/etc/ssh/sshd_config, specifying the CA public key for verifying user certificates, the host’s private key, and the host’s certificate:
# Path to the CA public key for verifying user certificates TrustedUserCAKeys /etc/ssh/ssh_user_key.pub # Path to this host's private key and certificate HostKey /etc/ssh/ssh_host_ecdsa_key HostCertificate /etc/ssh/ssh_host_ecdsa_key-cert.pub
On each client, add a line to
~/.ssh/known_hosts specifying the CA public key for verifying host certificates:
@cert-authority *.example.com ecdsa-sha2-nistp256 AAAAE...=
That’s it. That’s literally all that you need to do to start using certificate authentication. You can even use it alongside public key authentication to make transitioning easier.
Static keys in
~/.ssh/authorized_keys are no longer needed. Instead, peers learn one another’s public keys on demand, when connections are established, by exchanging certificates. Once certificates have been exchanged the protocol proceeds as it would with public key authentication.
Certificate authentication improves usability
With public key authentication, when you SSH to a remote host for the first time, you’ll be presented with a security warning like this:
$ ssh firstname.lastname@example.org The authenticity of host 'ec2-54-161-77-102.compute-1.amazonaws.com (184.108.40.206)' can't be established. ECDSA key fingerprint is SHA256:2ae53QcOB0W6HO+XtPmMXk7To/MvMuhFxTj8ZD7eSsE. Are you sure you want to continue connecting (yes/no)?
You’ve probably seen this before. If you’re like most people, you’ve been trained to ignore it by just typing “yes”. That’s a problem because this is a legitimate security threat. It’s also a pretty horrendous user experience. I’d wager the vast majority of SSH users don’t actually understand this warning.
When you SSH to a host, the host authenticates you. Your SSH client also attempts to authenticate the host. To do so your client needs to know the host’s public key. Host public keys are stored in a simple database in
~/.ssh/known_hosts. If your client can’t find the host’s public key in this database you get this warning. It’s telling you that the host can’t be authenticated!
What you’re supposed to do is verify the key fingerprint out-of-band by asking an administrator or consulting a database or something. But no one does that. When you type “yes” the connection proceeds without authentication and the public key is permanently added to
~/.ssh/known_hosts. This is the trust on first use (TOFU) anti-pattern.
Since certificate authentication uses certificates to communicate public key bindings, clients are always able to authenticate, even if it’s the first time connecting to a host. TOFU warnings go away.
Certificate authentication also offers a convenient place to gate SSH with custom authentication: when the certificate is issued. This can be leveraged to further enhance SSH usability. In particular, it let’s you extend single sign-on (SSO) to SSH. SSO for SSH is certificate authentication’s biggest party trick. We’ll return to this idea and see how it further enhances usability and security later. For now, let’s move on to operability.
Certificate authentication improves operability
Eliminating key approval and distribution has immediate operational benefits. You’re no longer wasting ops cycles on mundane key management tasks, and you eliminate any ongoing costs associated with monitoring and maintaining homegrown machinery for adding, removing, synchronizing, and auditing static public key files across your fleet.
The ability to issue SSH user certificates via a variety of authentication mechanisms also facilitates operational automation. If a cron job or script needs SSH access it can obtain an ephemeral SSH certificate automatically, when it’s needed, instead of being pre-provisioned with a long-lived, static private key.
SSH public key authentication introduces some weird operational constraints around host names that certificate authentication eliminates. As we’ve seen, when an SSH client connects to a host for the first time it displays a TOFU warning to the user. When the user types “yes” the host’s public key is added locally to
~/.ssh/known_hosts. This binding between the host name and a specific public key is permanent. If the host presents a different public key later, the user gets an even scarier host key verification failure error message that looks like this:
$ ssh email@example.com @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that a host key has just been changed. The fingerprint for the ECDSA key sent by the remote host is SHA256:2ae53QcOB0W6HO+XtPmMXk7To/MvMuhFxTj8ZD7eSsE. Please contact your system administrator. Add correct host key in ~/.ssh/known_hosts to get rid of this message. Offending ECDSA key in ~/.ssh/known_hosts:11 ECDSA host key for ec2-54-161-77-102.compute-1.amazonaws.com has changed and you have requested strict checking. Host key verification failed.
This makes it operationally challenging to reuse host names. If
prod01.example.com has a hardware failure, and it’s replaced with a new host using the same name, host key verification failures will ensue. This usually results in a bunch engineers contacting secops to tell them they’re being hacked.
Ignoring host key verification failures has the exact same attack surface area as not knowing the key at all. Curiously, OpenSSH chooses to soft-fail with an easily bypassed prompt when the key isn’t known (TOFU), but hard-fails with a much scarier and harder to bypass error when there’s a mismatch.
In any case, certificates fix all of this since a current name-to-public-key binding is communicated when a connection is established. Changing the host’s public key is fine, as long as the host also gets a new certificate. You can safely reuse host names and even run multiple hosts with the same name. You’ll never see a host key verification failure again. Beyond name reuse, we’ll soon see that eliminating host key verification failures is one of the many ways certificate authentication facilitates good security hygiene.
Certificate authentication improves security
While the SSH protocol itself is secure, public key authentication encourages a bunch of bad security practices and makes good security hygiene hard to achieve.
With public key authentication, keys are trusted permanently. A compromised private key or illegitimate key binding may go unnoticed or unreported for a long time. Key management oversight (e.g., forgetting to remove an ex-employee’s public keys from hosts) results in SSH failing open: unauthorized access without end.
Certificates, on the other hand, expire. In an incident — a mistake, theft, misuse, or key exfiltration of any form — compromised SSH credentials will expire automatically, without intervention, even if the incident goes unnoticed or unreported. SSH certificates are fail-secure. Access expires naturally if no action is taken to extend it. And when SSH users and hosts check in periodically with your CA to renew their credentials, a complete audit record is produced as a byproduct.
We’ve already seen how public key authentication trains users to ignore serious security warnings (TOFU) and triggers spurious security errors. This is more than an operational nuisance. Confusion caused by host key verification failure discourages host rekeying (i.e., replacing a host’s key pair). Host private keys aren’t very well protected, so periodic rekeying is good practice. Rekeying may be required after a breach or after offboarding a user. But, to avoid disruption from ensuing host key verification failures, it’s often not done. Certificate authentication makes rekeying hosts trivial.
Public key authentication also makes rekeying difficult for users. Key approval and distribution is annoying enough that users are reluctant to rekey, even if you’ve built tools to make it possible. Worse, frustrated users copy private keys and reuse them across devices, often for many years. Key reuse is a serious security sin. Private keys are never supposed to be transferred across a network. But SSH public key authentication exposes users directly to sensitive private keys, then fails to give them usable tools for key management. It’s a recipe for misuse and abuse.
An SSH CA, coupled with a simple command-line client for users, can streamline key generation and insulate users from a lot of unnecessary detail. Certificate authentication can’t completely eliminate all security risks, but it does facilitate SSH workflows that are more intuitive, easier to use, and harder to misuse.
An ideal SSH flow
SSH certificate authentication is the foundation of what I think is the ideal SSH flow.
To SSH, users first run a login command in their terminal (e.g.,
step ssh login):
$ step ssh login Your default web browser has been opened for you to login: https://accounts.google.com/...
A browser is opened and an SSO flow is initiated at your organization’s identity provider:
A web-based SSO flow makes it easy to leverage strong MFA (e.g., FIDO U2F) and any other advanced authentication capabilities your identity provider offers. Users login with a familiar flow, and removing a user from your canonical identity provider ensures prompt termination of SSH access.
Once the user completes SSO, a bearer token (e.g., an OIDC identity token) is returned to the login utility. The utility generates a new key pair and requests a signed certificate from the CA, using the bearer token to authenticate and authorize the certificate request.
The CA returns a certificate with an expiry long enough for a work day (e.g., 16-20 hours). The login utility automatically adds the signed certificate and corresponding private key to the user’s
Users needn’t be aware of any of this detail. All they need to know is that, in order to use SSH, they must first run
step ssh login. Once that’s done they can use SSH like normal:
$ ssh prod01.example.com Welcome to Ubuntu 18.04.2 LTS (GNU/Linux 4.15.0-1036-gcp x86_64) Last login: Wed Sep 11 04:04:51 2019 from 220.127.116.11 mmalone@prod01:~$
Like browser cookies, short-lived certificates issued by this flow are ephemeral credentials, lasting just long enough for one work day. Like logging into a website, logging into SSH creates a session. It’s a simple process that must be completed, at most, once per day. This is infrequent enough that strong MFA can be used without frustrating or desensitizing users.
New private keys and certificates are generated automatically every time the user logs in, and they never touch disk. Inserting directly into
ssh-agent insulates users from sensitive credentials. If a user wants to connect from a different device it’s easier for them to run
step ssh login there than it is to exfiltrate keys from
ssh-agent and reuse them.
There are lots of possible variations of this flow. You can adjust the certificate expiry, use PAM authentication at the CA instead of SSO, generate the private key on a smart card or TPM, opt not to use
ssh-agent, or move MFA to the actual SSH connection. Personally, I think this combination offers the best balance of security and usability. Indeed, relative to most existing SSH deployments it’s operationally simpler, more secure, and more usable.
Critics of SSH certificate authentication say that it’s new, not well supported, and the tooling doesn’t exist to use certificates in practice. The truth is, certificate authentication was added in OpenSSH 5.4 almost a decade ago. It’s battle tested and used in production by massive operations. And the tooling required to build this ideal SSH flow is available today.
There are lots of existing tools for managing SSH certificates. Here are a few:
ssh-keygencan generate root certificates and sign user & host certificates
netflix/blessis Netflix’s SSH CA that runs in AWS Lambda and uses IAM
nsheridan/cashieris Intercom’s SSH CA
uber/pam-usshlets you use certificates to authorize
hashicorp/vaulthas an SSH secrets engine
For our part, the most recent release of
v0.12.0) adds basic SSH certificate support. In other words:
step-cais now an SSH CA (in addition to being an X.509 CA)
stepmakes it easy for users and hosts to get certificates from
SSH workflows aren’t fully fleshed out yet, but these tools already do everything you need for the ideal flow.
With the appropriate configuration of
step-ca you can use
Get a host certificate automatically at startup
To demonstrate, let’s create a new EC2 instance with the
aws CLI tool. The interesting bits are tucked in some light configuration (using a user-data startup script) that gets a host certificate and enables certificate authentication for users:
$ aws ec2 run-instances --image-id ami-07d0cf3af28718ef8 \ --count 1 --instance-type t2.micro \ --key-name mike-test \ --security-group-ids launch-wizard-7 \ --user-data file://startup.sh
Note: you should be able to use our instance identity document support here, but we’ve got a few kinks to work out. Stay tuned.
Get a user certificate using SSO (OAuth OIDC)
Now we’ll use
step ssh certificate locally (you can
brew install step) to generate a new key pair, get a certificate from the CA using SSO, and automatically add the certificate and private key to
That sounds like a lot, but it’s just one command:
$ step ssh certificate firstname.lastname@example.org id_ecdsa ✔ Provisioner: Google (OIDC) Your default web browser has been opened to visit: https://accounts.google.com/o/oauth2/v2/auth?client_id=650... ✔ CA: https://ca.internal ✔ Private Key: id_ecdsa ✔ Public Key: id_ecdsa.pub ✔ Certificate: id_ecdsa-cert.pub ✔ SSH Agent: yes
Once that’s done we can SSH to the instance we just created, using certificate authentication, with no TOFU!
$ ssh email@example.com Welcome to Ubuntu 18.04.2 LTS (GNU/Linux 4.15.0-1044-aws x86_64) Last login: Thu Sep 12 02:25:43 2019 from 18.104.22.168 mike@ip-172-31-70-94:~$
There’s a lot more that can be done to make SSH certificate authentication even more awesome. We’re working on that. If you have any ideas, let us know!
Use SSH certificates
SSH certificate authentication does a lot to improve SSH. It eliminates spurious TOFU warnings and host key verification failures. It lets you drop complex key approval & distribution processes and extend SSO to SSH. It makes rekeying possible for hosts and easier than key reuse for users. It makes SSH keys ephemeral, making key management oversights fail-secure.
You can deploy an SSH CA and reconfigure hosts in a matter of minutes. It’s easy to transition — you can continue supporting public key authentication at the same time.
SSH certificate authentication is the right way to do SSH.
At smallstep, we’re looking forward to improving our SSH story. We’re building out infrastructure and streamlined workflows to make SSH better for everyone. And keep an eye on our blog because we have a lot more to say about SSH!