-
Notifications
You must be signed in to change notification settings - Fork 193
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
Expired Certificate #477
Comments
Thanks for the report. |
Hello, https://1000-sans.badssl.com expired yesterday as well, can you fix it too? |
The following have also expired: |
Hi, any update on this? |
1000/10000-sans unfortunately break most CA provisioning panels, so they require custom issuance and we have not been able to get these reissued yet. Do let me know if these are critical to any particular test suites (we do not use these in any of our manual testing flows) and I can see if we can come up with a more sustainable solution for renewing these yearly. no-subject and no-common-name are known (tracked in Issue #447) |
The new certificate for |
@christhompson I can help maintain some of these certificates, if needed, on behalf of Mozilla. My email address is [email protected]. Please reach out to me over email to discuss how I can help. |
@christhompson, Are there any plans to update certificates for them? |
https://reversed-chain.badssl.com/ also expired. |
As the CA Program Manager at Mozilla, I have connections with Certification Authorities that issue these kinds of certificates. I'm sure I can get valid certificates from these CAs, as long as they do not violate the current CABF Baseline Requirements. |
I can get these certificates issued for:
Who is maintaining the webserver? |
Thanks for the offer @BenWilson-Mozilla -- I've sent you an email to discuss further. |
BTW I think |
That's correct. See #501 |
The following certificates have expired recently:
And https://no-sct.badssl.com will expire in several days.
The text was updated successfully, but these errors were encountered: