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

consider adding notyet.badssl.com (future notBefore) #495

Open
jschauma opened this issue Feb 18, 2022 · 2 comments
Open

consider adding notyet.badssl.com (future notBefore) #495

jschauma opened this issue Feb 18, 2022 · 2 comments

Comments

@jschauma
Copy link

It might be useful to have a test to verify validation of the 'notBefore' date. I don't know how far in the future CAs let you request a cert, so there would eventually be a renewal needed once the future date becomes present/past.

@hgc81538
Copy link

I think it is hard to find a CA to issue such cert.

You might change your computer clock to simulate.

@ldemailly
Copy link

ldemailly commented Apr 23, 2023

could be a self signed future cert I suppose, off self-signed.badssl.com for instance
(only issue will be remember to not have become current, like the current issue with the other certs having expired)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants