Add lint to check that the notBefore timestamp is not too early compared to the SCTs#1022
Merged
christopher-henderson merged 21 commits intoFeb 15, 2026
Merged
Conversation
christopher-henderson
approved these changes
Feb 15, 2026
christopher-henderson
left a comment
Member
There was a problem hiding this comment.
Clean and easy lint, thank you!
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
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.
Following a recent incident, as seen on bugzilla, I thought it would be useful to develop a simple lint that verifies compliance with §7.1.2.7 of the CABF TLS BRs, which requires that...
In general, there is no way to determine, by just examining a certificate, when it was signed. However, since the certificate signing time cannot be earlier than the timestamps included in any SCTs, verification is possible when the certificate includes SCTs, as is done in this lint.