This translation is provided for informational purposes only. In case of doubt, the German version is authoritative.

ssh-ca

← Software

ssh-ca: a public key is signed by your own SSH CA. The time-limited certificate is accepted by every server that trusts the CA; each issuance is recorded.

SSH access that expires on its own – instead of keys that last forever.

Plain SSH keys never expire, are not tied to a person and must be maintained in authorized_keys on every server. ssh-ca turns SSH keys into time-limited certificates issued by your own certificate authority: the servers trust the CA once, and you grant access centrally with two commands.

Grant access centrally and keep a traceable record.

  • Time-limited, not permanent. Every certificate has a validity period – 30 days by default, freely adjustable. Once it has expired, OpenSSH no longer accepts the certificate, without you having to remove keys from your servers.
  • Less maintenance on the servers. Instead of many individual keys, the servers only hold the CA's public key. Principals define which user accounts a certificate is valid for.
  • Traceable issuance. ssh-ca keeps a list of all issued certificates and sets up the CA as a Git repository by default: each signature is recorded as a commit with identity, validity and principals. The CA's private key is kept out of Git.

For administrators and IT teams who run several Linux/Unix servers with OpenSSH and want to grant time-limited access to staff or contractors centrally – without a full-blown PKI. Requirements: Perl 5.28 or later, ssh-keygen and optionally Git.

A lean command-line tool. ssh-ca is a Perl command-line program with the commands init and sign. The only Forgejo release so far is 1.0 (2021); the latest version tag, 1.3.0, dates from 2022; later fixes are still unreleased. ssh-ca is open source under Apache-2.0. Certificate revocation and host certificates are not supported; a rewrite in Go has been started but is not yet usable.

Introduce SSH certificates in your environment.

We set up your SSH CA, configure your servers and integrate certificate issuance into your processes. Tell us how many servers and users you have – we will discuss the right setup with you.

Request a quote

News

The only published Forgejo release is 1.0. Versions 1.1.0 to 1.3.0 exist only as Git tags and are listed here as milestones. No new version has appeared since July 2022; unreleased development work is labelled as such.

Unreleased — development state (master)
After 1.3.0, without a version or release (not yet available as a package or release): certificates can now also be issued with CA keys of types other than RSA (e.g. Ed25519); ssh-keygen failures result in a non-zero exit code; multiple principals are recorded correctly in the list of issued certificates. The README now describes operation, an Apache-2.0 licence file is included and a regression test covers init and sign. Open wish without a date: revocation lists for certificates.
— Version tag 1.3.0
1.3.0: Version tag 1.3.0 (not a Forgejo release): multiple principals are now sorted, so certificates for the same combination are stored in the same place regardless of the order in which they were given.
— Version tag 1.2.0
1.2.0: Version tag 1.2.0 (not a Forgejo release): the identity (-i/--identity) is now mandatory when signing, so no certificates without an identity are created.
— Version tag 1.1.0
1.1.0: Version tag 1.1.0 (not a Forgejo release): pending key requests for an identity are found automatically; with --push the CA's Git repository is pushed right after signing.
— Release 1.0
1.0: First release: several public keys of one identity can be signed in a single run; every certificate gets a unique serial number.

Source code and documentation · All available releases

schlittermann.de    KEYS: GnuPG  |  SSH  |  X509 || Linux User Group Dresden

acd6d9e · 2026-11-06 09:14:34 +0100 · Heiko Schlittermann (ai)

The live chat button uses necessary cookies. By using our website, you agree to their use.  Accept