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.

Sign up for GitHub

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

Jump to bottom

self-signed certificate has expired #418

Closed
djcater opened this issue Oct 9, 2019 · 1 comment · May be fixed by #419
Closed

self-signed certificate has expired #418

djcater opened this issue Oct 9, 2019 · 1 comment · May be fixed by #419

Comments

@djcater
Copy link

djcater commented Oct 9, 2019

https://self-signed.badssl.com/

I see that the auto-generating part was removed, but I think the static in-repo certificate should be regenerated as per: "we'll just track the expiration and regenerate in-tree when needed" from #390 (comment)_
christhompson added a commit that referenced this issue Oct 9, 2019
@christhompson
Update wildcard-self-signed.pem
957984d 
Update with a re-generated self-signed certificate (the previous one had expired, and I forgot to check in my previous re-generated one into the repository). Fixes #418.
@christhompson christhompson mentioned this issue Oct 9, 2019
Open
@christhompson
Copy link
Collaborator

Ahh, same bug as in #417 -- thanks for catching these. I've made a note to myself in my deploy playbook and updated this one as well. This should be fixed on the site and #419 will make it so I don't accidentally pull in the expired one from the repo again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update wildcard-self-signed.pem chromium/badssl.com
2 participants
@christhompson @djcater