3 ms·
The certificate is expiring in less than three months. Chrome has always been clear that they don't care about SHA-1 certs that are expiring within 2015. They j
by geofft 12y ago
The certificate is expiring in less than three months. Chrome has always been clear that they don't care about SHA-1 certs that are expiring within 2015. They just want to make sure that when you renew those certs, you renew as SHA-256.
http://googleonlinesecurity.blogspot.com/2014/09/gradually-sunsetting-sha-1.html http://googleonlinesecurity.blogspot.com/2014/09/gradually-s...
"Sites with end-entity certificates that expire between 1 January 2016 and 31 December 2016 (inclusive), and which include a SHA-1-based signature as part of the certificate chain, will be treated as 'secure, but with minor errors' [i.e., the lock-with-yellow-triangle you also get for mixed content].
"Sites with end-entity certificates that expire on or after 1 January 2017, and which include a SHA-1-based signature as part of the certificate chain, will be treated as 'affirmatively insecure'. Subresources from such domain will be treated as 'active mixed content'."
- Osiris 12y agoThis just hit me. I was doing some work on my side-business site and noticed a big red error for the SSL cert. Luckily the process to reissue a new cert was pretty straight forward and I gotten taken care of the same day. My SSL provider (namecheap) did send me one email at some point, but I'm sure I glossed over it because I didn't realize this change was coming.