This notification is intended for all customers who are using our DNS service and have Securly certificates deployed. As you might know, the Securly certificate is responsible to decrypting SSL traffic that come from hosts on your network that use the Securly DNS service for filtering.
Securly Certificate Replacement
Please plan on deploying the attached (new) certificate on your non-Chromebook devices by March 30th. While doing so, it is important that you DO NOT delete your old Securly certificate.
Both Microsoft (http://blogs.technet.com/b/
pki/archive/2013/11/12/sha1- deprecation-policy.aspx) and Google (http://googleonlinesecurity. blogspot.com/2014/09/ gradually-sunsetting-sha-1. html) have announced their intent to deprecate support for the SHA-1 algorithm. Our current certificate is signed using the SHA-1 hash algorithm. The new certificate is signed using the favored SHA-256 hash algorithm.
Deploying the new certificate will allow your users to continue browsing while maintaining a high level of confidence (no strange untrusted certificate errors thrown by browsers) in the systems that they use for instructional and classroom purposes.
On March 30th, we will end support for the current Securly certificate and switch support to the new certificate.
Should you have any questions about this change, please do not hesitate to contact us by writing to firstname.lastname@example.org.