-
Notifications
You must be signed in to change notification settings - Fork 252
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Testing certificates for verdancy #398
Labels
Comments
tashian
added
enhancement
needs triage
Waiting for discussion / prioritization by team
labels
Dec 16, 2020
tashian
changed the title
Testing certificates for ripness
Testing certificates for ripeness
Dec 16, 2020
This comment has been minimized.
This comment has been minimized.
tashian
changed the title
Testing certificates for ripeness
Testing certificates for verdancy
Dec 17, 2020
|
tashian
added a commit
to smallstep/docs-old
that referenced
this issue
Dec 23, 2020
Merging this for now, and I'll come back and replace the `jq` usage once smallstep/cli#398 is released.
Can we do this for SSH certs too? This would allow the same systemd renewal method for SSH host certs. |
Merged
Closed
Merged
step certificate needs-renewal addresses this issue and was merged in #495 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'd love to be able to know whether or not a certificate is about to expire, without running something like:
For scripting purposes, I'd love a command such as
step certificate verify --verdancy
that would simply say whether or not the certificate is ready for renewal, and return an exit code:The text was updated successfully, but these errors were encountered: