<![CDATA["Encountered an internal error in the SSL library" Office2010/Windows7 using unsecure protocols]]>Since the last GoFAST version (GoFAST 3.5.2) we prohibit protocols with known security vulnerabilities (more particularly TLSv1.0 and TLSv1.1). The TLSv1.0 protocol is also prohibited by the PCI-DSS bank payment standard.

On the other hand under Windows7 / Office 2010, Microsoft leaves the use of these protocols insecure by default, this being refused by GoFAST and which prevents the opening under Office 2010 "The application encountered an internal error loading the SSL libraries . "

The Microsoft procedure to comply with last security policy is here : https://support.microsoft.com/en-us/help/3140245/update-to-enable-tls-1-1-and-tls-1-2-as-default-secure-protocols-in-wi

]]>https://community.ceo-vision.com/topic/256/encountered-an-internal-error-in-the-ssl-library-office2010-windows7-using-unsecure-protocolsRSS for NodeWed, 30 Dec 2020 16:34:19 GMTSun, 23 Feb 2020 10:00:48 GMT60<![CDATA[Reply to "Encountered an internal error in the SSL library" Office2010/Windows7 using unsecure protocols on Sun, 23 Feb 2020 10:02:37 GMT]]>Since the last GoFAST version (GoFAST 3.5.2) we prohibit protocols with known security vulnerabilities (more particularly TLSv1.0 and TLSv1.1). The TLSv1.0 protocol is also prohibited by the PCI-DSS bank payment standard.

On the other hand under Windows7 / Office 2010, Microsoft leaves the use of these protocols insecure by default, this being refused by GoFAST and which prevents the opening under Office 2010 "The application encountered an internal error loading the SSL libraries . "

The Microsoft procedure to comply with last security policy is here : https://support.microsoft.com/en-us/help/3140245/update-to-enable-tls-1-1-and-tls-1-2-as-default-secure-protocols-in-wi

]]>https://community.ceo-vision.com/post/651https://community.ceo-vision.com/post/651Sun, 23 Feb 2020 10:02:37 GMT<![CDATA[Reply to "Encountered an internal error in the SSL library" Office2010/Windows7 using unsecure protocols on Mon, 24 Feb 2020 09:44:29 GMT]]>I encountered this issue when first trying to use "edit from my PC"; applying the Microsoft procedure to update the prototols indeed solved it. The process requires two steps (1. install, 2. correct registry)
Need to apply that update on all clients supposed to use the functionality

]]>https://community.ceo-vision.com/post/654https://community.ceo-vision.com/post/654Mon, 24 Feb 2020 09:44:29 GMT