Skip to content
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

[Bug]: step ca rekey does not create new keys when used with the --daemon flag #1343

Open
mikerquinn opened this issue Jan 9, 2025 · 0 comments
Assignees
Labels
bug needs triage Waiting for discussion / prioritization by team

Comments

@mikerquinn
Copy link

mikerquinn commented Jan 9, 2025

Steps to Reproduce

step ca rekey ssl-cert.pem ssl-cert.key --force --exec post_renew.sh works like it should but
step ca rekey ssl-cert.pem ssl-cert.key --force --exec post_renew.sh --rekey-period 1m --daemon just renews without a new key

Your Environment

  • OS - Linus Ubuntu 24.04
  • step CLI Version - Smallstep CLI/0.27.2 (linux/amd64)
    Release Date: 2024-7-18T18:15:09Z

Expected Behavior

I expected the certificate to be renewed with a new private key.

Actual Behavior

It is renewed with the same key, same as if you had run step ca renew. This only happens when running with the --daemon flag.

Additional Context

Brought this up on the Discord and "Dopey" requested that I put in an issue.

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

@mikerquinn mikerquinn added bug needs triage Waiting for discussion / prioritization by team labels Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug needs triage Waiting for discussion / prioritization by team
Projects
None yet
Development

No branches or pull requests

2 participants