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

Expired Certificate #477

Open
shankerwangmiao opened this issue Oct 9, 2021 · 14 comments
Open

Expired Certificate #477

shankerwangmiao opened this issue Oct 9, 2021 · 14 comments

Comments

@shankerwangmiao
Copy link

The following certificates have expired recently:

And https://no-sct.badssl.com will expire in several days.

@christhompson
Copy link
Collaborator

Thanks for the report. untrusted-root and self-signed should be replaced now, but no-sct and revoked are waiting on validation with our CA -- hopefully I can get those updated very soon.

@ghost
Copy link

ghost commented Oct 14, 2021

Hello, https://1000-sans.badssl.com expired yesterday as well, can you fix it too?

@uplime
Copy link

uplime commented Oct 20, 2021

The following have also expired:
https://no-subject.badssl.com/
https://no-common-name.badssl.com/

@bratkartoffel
Copy link

Hi, any update on this?

@christhompson
Copy link
Collaborator

christhompson commented Oct 27, 2021

  • We've regenerated the revoked.badssl.com cert -- once it has been added to CRLSet I'll push the new cert live to the site.
  • no-sct should now be updated with a new certificate.

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)

@christhompson
Copy link
Collaborator

The new certificate for revoked.badssl.com is now in Chrome's CRLSet and the server certificate has updated to match.

@BenWilson-Mozilla
Copy link

@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.

@AenBleidd
Copy link

AenBleidd commented Dec 8, 2021

@christhompson,
These domains still have expired certificates:

Are there any plans to update certificates for them?

@billchenchina
Copy link

https://reversed-chain.badssl.com/ also expired.

@BenWilson-Mozilla
Copy link

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.

@BenWilson-Mozilla
Copy link

I can get these certificates issued for:

https://1000-sans.badssl.com/
https://no-subject.badssl.com/
https://no-common-name.badssl.com/

Who is maintaining the webserver?

@christhompson
Copy link
Collaborator

Thanks for the offer @BenWilson-Mozilla -- I've sent you an email to discuss further.

@snim2
Copy link

snim2 commented Apr 2, 2022

BTW I think sha384.badssl.com and sha512.badssl.com expired on Friday.

@szh
Copy link

szh commented May 24, 2022

BTW I think sha384.badssl.com and sha512.badssl.com expired on Friday.

That's correct. See #501

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

10 participants