This is where I write about Linux and about running my own servers, at home and on rented VPS. Most posts are long and technical. They show every step, the code that goes with it and the reasons behind my decisions, so that you can build the same thing yourself. They also show what went wrong on the way.
The last step to certificate-only SSH: authorized_keys managed exclusively, one break-glass key that lives only in pass and ssh-agent, 30-day certificates for a tablet, what to do with a lost device, and the ways I nearly locked myself out.
A Forgejo Actions job proves who it is with its OpenID Connect token, OpenBao checks the repository and branch and signs a five-minute SSH certificate, and the target host allows that certificate exactly one command. No secret is stored in the CI system.
The Ansible side of SSH certificates: sshd trusts the user CA, principals files with options the host enforces, revoked keys, host certificates signed during the playbook run, and a small client script plus one known_hosts line on the laptop.
OpenBao as a rootless Podman quadlet with Raft storage behind Traefik, reachable only from the LAN and WireGuard: init, unseal, the whole configuration as an idempotent script (SSH CAs, roles, policies, OIDC login through Forgejo), and backup and restore with Raft snapshots.
What is wrong with authorized_keys files and trust on first use, how OpenSSH certificates work (user and host CAs, principals, validity, options), a hands-on demo with ssh-keygen, and why I run the CA on OpenBao.