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

Configuration parameter for certificate lifetime. #251

cpu opened this issue Jul 11, 2019 · 0 comments


None yet
1 participant
Copy link

commented Jul 11, 2019

Boulder allows configuration of issued end entity certificate lifetime. Pebble presently hard-codes it:


Line 197 in 0abe052

NotAfter: time.Now().AddDate(5, 0, 0),

RFC 8555 7.5 specifies that a new order request may have optional notBefore and notAfter fields as one way to have configurable certificate lifetimes. I'm not keen on implementing this in Pebble because I feel like it was a specification mistake to give server's no ability to adjust the requested dates (e.g. to back date). It's extremely unlikely we would implement processing of these order fields in Boulder, even if we allowed shorter certificate lifetimes.

Rather than implement the notBefore/notAfter fields of RFC 8555 I think Pebble should follow Boulder's lead and make the static certificate lifetime configurable in the Pebble config file loaded at startup. This is a simple solution that would meet the needs of developer requests like this.

@cpu cpu added the enhancement label Jul 11, 2019

jernst added a commit to uboslinux/ubos-packages that referenced this issue Jul 12, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.