If someone can point me into the right direction, that would be great. What am I missing here? I have Googled around, and it seems that I don't need to re-issue CA after enabling the TLS 1.2. Unfortunately, I still in the same situation. The latest version of TLS that is available on the Windows XP platform is TLS 1.0 and cannot be used to establish secure connections. I tried to re-issue another certificate since the restart, hoping the new issued certificate will support TLS 1.2. SocketTools uses the Windows CryptoAPI and Schannel security provider to provide support for Transport Security Layer (TLS), which is used with secure connections. The server has also been restarted to apply this change. To enable TLS 1.2 on a Windows Server 2008 machine: Log into the machine with Administrator privileges. I have enabled TLS 1.2 in my Windows Server 2019 via the Registry Key ( Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2). Based on this, I knew that my certs have been issued under TLS 1.0.
If I disable the TLS 1.0, I got error: "Can't connect securely to this page". IE with TLS 1.0 enable can load the site without any issues. The error message in Chrome and MS Edge Enterprise is: ERR_CONNECTION_CLOSED. However, all sites with this cert (the one that has been issued from my CA), Chrome will not load the page. I need to use my local Windows Server 2019 Certificate Authority to issue cert for webserver.
0 kommentar(er)
