" sha256 Archives - LuxSci FYI Blog: Learn about HIPAA email encryption, secure email encryption, and more

Posts Tagged ‘sha256’

End of Life for LuxSci Internet Explorer 8 on XP Support

Sunday, August 2nd, 2015

As of November 1st, 2015, LuxSci will no longer support Internet Explorer versions 8 and below on Windows XP.  We will still support Internet Explorer v8 on Windows Vista and above (for a while).

What will be the effect of the dropped support?  Sometime after November 1st, 2015, users of Internet Explorer 8 on XP may no longer be able to connect to LuxSci.com or any web sites hosted by LuxSci, due to its lack of support for modern Internet security and usage features.

For customers who still use Internet Explorer 8 on XP, we recommend installing the latest version of FireFox or Google Chrome, as these will work fine even on very old operating systems, such as Windows XP, and will provide support for features we are enabling, which Internet Explorer 8 on XP does not support.

What is actually changing?

LuxSci will be making 2 changes after November 1st:

Read the rest of this post »

New SSL Certificates, SHA256, and Backwards Incompatibility: What to Do?

Wednesday, October 22nd, 2014

Thanks to Google,” web sites around the world are updating their SSL certificates to use a newer “hashing” algorithm called “SHA256”.  Indeed, all new SSL certificates that LuxSci obtains for its customers will use SHA256, going forward (unless you don’t want that).

Read on to discover why this change is happening, what it means, why everyone is upset with Google for forcing the issue, and what your options are.

What’s the problem?

SHA1 is a method for making digital signatures and is used in the SSL certificates by most sites on the web.  There is currently no security issue with SHA1 and computer power is not expected to be sufficient to “crack” SHA1 until sometime in the 2020s.  In fact, Microsoft has stated, and the Internet community has agreed back in 2013, that it should be phased out by 2017 … well before the danger zone and giving folks plenty of time to transition.

Note: There is currently no known issue with SHA1 or any expectation that it is vulnerable or can be compromised now.

Read the rest of this post »