Encrypted stories, by FeatheredTar
Due to Google’s policy change that all certificates must be signed with a minimum of SHA256, I recently replaced the cert on this site. Some of you have let me know that SSL errors were popping up. One was due to a missed “https” on the MailChimp signup form, the other was due to Symantec (VeriSign)’s new root cert that is also signed using SHA256.
If you are currently using a certificate on your SSL site that is signed using the SHA-1 algorithm, you should consider replacing that cert soon. Chrome will soon be configured to warn users going to those sites about the weak signature. Enterprise customers, this is going to be as painful as Heartbleed if you had potentially compromised keys.
As it turns out, Apple devices did not have this cert yet, and it is installed either with the OS X 10.9.5 update or the Safari 7.1 update. If you are still getting an SSL error, please make sure your Mavericks installation is up to date.
Possibly Related Posts:
- Top Posts from 2015
- October 2015 Roundup
- September 2015 Roundup
- August 2015 Roundup
- June-July 2015 Roundup