Hey folks,
sorry about the negligence on my part. This is just to let everyone know that I’m aware of it.
I already sent the CSR to StartSSL, so this will hopefully be resolved later today.
// Oliver
Update:
This should be fixed now.
- SHA256 fingerprint:
78:A1:7D:C5:A9:45:39:B9:64:5A:F9:85:8B:AA:82:9A:92:2B:76:23:46:46:E5:8A:E5:E7:75:E4:6E:27:B1:B1 - SHA1 fingerprint:
6C:F0:65:0D:30:34:AE:D8:3B:15:CD:32:A0:5A:31:81:EF:F3:36:41
Something to look into as the year progresses that might save you some time in the future. https://letsencrypt.org/
Let’s Encrypt’s goal is to never have to manually deal with a domain validated certificate.
Yep, I’m aware of it. Unfortunately it wasn’t available just yet. However, with StartSSL I pay once every two years for the validation of me as individual and then only need to validate domain access after that.
As soon as letsencypt becomes available, I’ll probably move to it altogether.
The code signing certs from StartSSL also come with a huge caveat: signatures expire along with the cert. So I’ll have to move to VeriSign which is a bit more expensive, but what the heck.