BrowseSecurity & networking tools
Step CLI
Command-line tool for building, operating and automating PKI workflows, X.509 and crypto operations, and a client for the step-ca certificate authority.
Tested on Linux
Use it
Linux x86_64
download and extract official step_linux_amd64 tarball
mkdir -p ~/.local/bin /tmp/step && curl -fsSL -o /tmp/step/step.tgz https://dl.smallstep.com/cli/docs-cli-install/latest/step_linux_amd64.tar.gz && tar -xzf /tmp/step/step.tgz -C /tmp/stepinstall binary into ~/.local/bin and print version
install -m 755 /tmp/step/step_linux_amd64/bin/step ~/.local/bin/step && step version
Check that it works
install -m 755 /tmp/step/step_linux_amd64/bin/step ~/.local/bin/step && step versionThe output should contain “Smallstep CLI/0.31.0 (linux/amd64)”.
First thing to try
install -m 755 /tmp/step/step_linux_amd64/bin/step ~/.local/bin/step && step versionRun step version to confirm it works, then step help to see the available commands.
What it does
- Create, revoke, check and bundle X.509 certificatesTested
How to use it
- Create a root CA with
step certificate create "<root name>" root.crt root.key --profile root-ca --no-password --insecure -f, then a leaf with `step certificate create <hostname> leaf.crt leaf.key -- - Check the leaf against the root with
step certificate verify leaf.crt --roots root.crt. - Bundle the certificates with
step certificate bundle leaf.crt root.crt bundle.crtand view one withstep certificate inspect leaf.crt --short.
- Create a root CA with
- Run and use a step-ca or ACME certificate authorityTested
How to use it
- Set up a new CA with
step ca init --ssh --name <CA name> --dns <hostname> --address <ip:port> --provisioner <email> --password-file <file> --deployment-type standalone. - Look for the message "Your PKI is ready to go."
- Run
step help cato see how to issue certificates for your services.
- Set up a new CA with
- Work with JWTs and JOSE objectsTested
How to use it
- Create a key pair with
step crypto jwk create pub.json priv.json --kty EC --no-password --insecure -f. - Sign a token with
step crypto jwt sign --key priv.json --iss <issuer> --aud <audience> --sub <subject> --exp <unix time> < /dev/null > <file>. - Verify it with
step crypto jwt verify --key pub.json --iss <issuer> --aud <audience> < <file>.
- Create a key pair with
- Create and manage SSH certificatesNot tested
How far pickfit got
Linux x86_64
- Installs
- Starts
- 3 of 4 features work
- Works offline
macOS and Windows: the project says it runs there; pickfit hasn’t tried it.
Good for
- inspect a remote server's TLS certificate
- sign, verify and inspect JWTs
- generate and verify TOTP tokens
- get OAuth access tokens at the command line
How pickfit tested it
Each run starts from a clean machine and follows the steps above. How pickfit verifies
Linux x86_64
Its main function works
- Replayed from scratch
- Works offline
- Checked on 15 Nov 2026
- Version Smallstep CLI/0.31.0
Differences the test machine hit
- README: apt-get / dnf / pacman / apk install step-cli (run as root)
In the test: No root here; used the official Linux binary tarball from dl.smallstep.com/cli/docs-cli-install/latest/step_linux_amd64.tar.gz and copied bin/step to ~/.local/bin - README: step certificate inspect https://smallstep.com
In the test: Works (cmd 3) but needs network access, so not cited as an offline smoke test - README: step crypto jwt sign (payload optional)
In the test: Without a payload argument it waits on stdin; redirect < /dev/null when non-interactive - README: step ssh certificate with offline step-ca
In the test: Offline mode prompts on /dev/tty for the CA key password; had to add "password" to $STEPPATH/config/ca.json for non-interactive use