Certificate expiration #149

SilentT-FR opened this Issue Apr 12, 2015 · 6 comments


None yet

2 participants


The certificate Expires On 4/12/2015 2:35.

@ydahhrk ydahhrk added this to the 3.3.2 milestone Apr 13, 2015
ydahhrk commented Apr 13, 2015

Thank you.

ydahhrk commented Apr 14, 2015

This is already fixed.

Google Chrome reports the encryption algorithm could be stronger, and this is being looked into.
(This is also out of my control, so I don't have a due date, but I might in the near future.)
This is not likely a new quirk.

Thankfully, we can now at least release version 3.3.2, though I'd rather not close this issue until the encryption is upgraded.

ydahhrk commented Jun 15, 2015

Grade is now C.
At least :)

ydahhrk commented Nov 10, 2015


https://nicmx.github.io/jool-doc is the new core URL of the site. It uses Github's certificate, whose deployment grades A.

www.jool.mx is now a CNAME that simply points to nicmx.github.io, so it can still be used to reach the site when the full obnoxious URL can't be scratched out of the top of the head.

It's not perfect, because it means **https://**www.jool.mx doesn't work anymore, though **https://**nicmx.github.io/jool-doc does. This is a problem most custom Github domains share (workarounds exist, but aren't that secure).

On the other hand however, where it works, it works better. Whenever a secure channel is needed, just use the full URL.

Since we've essentially transferred the problem to Github, I'm going to close this issue. If Github finds a way to make TLS'd custom domains succeed that requires intervention from us, or if there are objections, feel free to reopen.

@ydahhrk ydahhrk closed this Nov 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment