CSC-31: Maximum Validity Reduction (#48)#51
Merged
XolphinMartijn merged 4 commits intomainfrom Nov 17, 2025
Merged
Conversation
* Update CSBR.md for proposed validity period change Updating to mostly match ian's original verbiage. However, given that we want at least 6 months to reflect the change after enforcmeent, setting the date to January 1st of 2026 instead of the original June 15th of 2025 * Update CSBR.md removing previous line to avoid confusion, and updating to March * Update docs/CSBR.md accepting change in verbiage to be clear on certificate life for certificates issued before Co-authored-by: Corey Bonnell <dev@cbonnell.com> * Update docs/CSBR.md removing an extra space Co-authored-by: Corey Bonnell <dev@cbonnell.com> --------- Co-authored-by: Corey Bonnell <dev@cbonnell.com>
barrini
approved these changes
Nov 17, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updating to mostly match ian's original verbiage. However, given that we want at least 6 months to reflect the change after enforcmeent, setting the date to January 1st of 2026 instead of the original June 15th of 2025
removing previous line to avoid confusion, and updating to March
accepting change in verbiage to be clear on certificate life for certificates issued before
removing an extra space