New self-signed SSL certificate going in tomorrow...

[LowWaterMark]

With the first year's certificate expiring, I've created a new one for the next 12-month period.

I'm still going with the self-signed approach since the past 12 months has not increased most people's confidence in the CA system, or shown that this particular forum needs a CA signed certificate. (If anything, this past year's "happenings" may have decreased CA confidence levels.)

I'll be putting it in place tomorrow, mid-day some time. Once it is in, if you use https access, you will receive a new warning about the certificate change, assuming you've saved the previous one in your browser(s) as I have. You can choose to save the new cert, which will prevent future warnings, if you prefer. I did that for the first year, and it worked well for me.

If you want to manually verify the new certificate, see the fingerprints below:

Fingerprints
SHA-1: AB FA 84 33 D0 5D 4F 9E 38 1C D2 FD FD 79 87 F8 5E FB 3C 7E
SHA-256: B0 5A DA E9 81 9C 5B AE EB 7C 2C D4 D1 C2 A9 77 49 E5 47 31 8C 12 87 5F 02 79 90 A4 8B CC C7 33


In image:

[LowWaterMark]

This has just been done. New cert is now in place.

[Cudni]

It prompted me not a minute ago to changee. Active now. Thanks

[ronjor]

Looks okay here.

[Tarnak]

I just accepted it.