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

Allow certificate lifetimes to be given in d,mo,y as well as hours. #1182

Open
sshipway opened this issue May 27, 2024 · 0 comments
Open

Allow certificate lifetimes to be given in d,mo,y as well as hours. #1182

sshipway opened this issue May 27, 2024 · 0 comments
Assignees
Labels
enhancement needs triage Waiting for discussion / prioritization by team

Comments

@sshipway
Copy link

Hello!

  • Vote on this issue by adding a 👍 reaction
  • If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

Currently, certificate lifetimes can only be given in hours, minutes and seconds. If you want to create a cert with a 90 day life, you cant say --not-after 90d but instead have to put --not-after 2160h

We should be able to use time periods in days or years; months might be awkward as they are different lengths and the 'm' would clash with 'minutes' but maybe '1M' could mean '30d'?

I would like to be able to use time windows such as

  • --not-after 1y
  • --not-after 90d
  • --not-after 3mo (this one I could live without though)

Why is this needed?

This is a relatively simple change that would be a bit improvement on usability when creating longer-lived certificates such as for hosts and services, which typically want to live for 90 days or 1 year. Giving longer times in hours is confusing and error-prone.

@sshipway sshipway added enhancement needs triage Waiting for discussion / prioritization by team labels May 27, 2024
@hslatman hslatman self-assigned this Jun 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement needs triage Waiting for discussion / prioritization by team
Projects
None yet
Development

No branches or pull requests

2 participants