Accessing TLS 1.3 Website from Windows Server 2012 R2 - ssl

I am having Windows Server 2012 R2 and I need to access a website whose SSL Certificate is using TLS 1.3 (Screenshot below)
But I get this error in my browser (IE 11)
This page can’t be displayed
Turn on TLS 1.0, TLS 1.1, and TLS 1.2 in Advanced settings and try connecting to [WEBSITE] again. If this error persists, it is possible that this site uses an unsupported protocol or cipher suite such as RC4 (link for the details), which is not considered secure. Please contact your site administrator.
Is there a way to access this website in IE 11 on Windows Server 2012 R2 ?
Thanks,

Seems, no. There is no way currently because IE 11 does not support TLS1.3.
Please try to use another browser.
Last updated on : 2022-06-30
Browser Compatibility:
TLS 1.3 on IE is fully supported on None of the versions, partially supported on None of the versions, and not supported on 5.5-11 IE versions.
TLS 1.3 on Edge is fully supported on 79-103, partially supported on None of the versions, and not supported on 12-18 Edge versions.
TLS 1.3 on Firefox is fully supported on 63-104, partially supported on 60-62, and not supported on 2-59 Firefox versions.
TLS 1.3 on Chrome is fully supported on 70-106, partially supported on None of the versions, and not supported on 4-69 Chrome versions.
TLS 1.3 on Safari is fully supported on 14.1-16, partially supported on 12.1-13, and not supported on 3.2-12 Safari versions.
TLS 1.3 on Opera is fully supported on 57-87, partially supported on None of the versions, and not supported on 9.5-56 Opera versions.
TLS 1.3 on Safari on iOS is fully supported on 12.2-16, partially supported on None of the versions, and not supported on 3.2-12 Safari on iOS versions.
TLS 1.3 on Android Browser is fully supported on 97-103, partially supported on None of the versions, and not supported on 2.3-4 Android Browser versions.
TLS 1.3 on Opera Mobile is fully supported on 64-64, partially supported on None of the versions, and not supported on 10-12 Opera Mobile versions.
TLS 1.3 on Chrome for Android is fully supported on 97-103, partially supported on None of the versions, and not supported on below 97 Chrome for Android versions.
TLS 1.3 on Firefox for Android is fully supported on 95-101, partially supported on None of the versions, and not supported on below 95 Firefox for Android versions.
TLS 1.3 on Samsung Internet is fully supported on 10.1-17, partially supported on None of the versions, and not supported on 4-9.2 Samsung Internet versions.

Related

Support for TLSv1 in Python 3.10.5/Twisted 22.4.0

I recently upgraded a server based on Python 3.8.6 to Python 3.10.5
The Twisted listener in it allows various devices to connect
Some of those devices only have TLSv1.
The server code specifically enables TLSv1/1.1/1.2/1.3 but only 1.2 and 1.3 work.
According to this issue https://bugs.python.org/issue43998 Python SSL no longer supports less than v1.2. But twisted uses pyOpenSSL, and I cannot find any documentation that states it only supports v1.2 and later.
Can anybody please supply some information on this.

Website denies some crawlers/browsers access but not others

You probably think that this is a misbehaving crawler problem but this CloudFlare website:
Blocks Internet Explorer on Windows 10 desktop (uses Windows API for HTTP)
Allows Edge on Windows 10 desktop (uses Windows API for HTTP?)
Blocks my crawler on Windows using WinInet Windows API for HTTP
Allows my crawler on Mac using Mac API for HTTP
Accordingly to this Internet Explorer 7 on Windows Vista should be support on even free CloudFlare:
https://support.cloudflare.com/hc/en-us/articles/203041594-Cloudflare-SSL-cipher-browser-and-protocol-support
I am in preliminary research phase, but it feels like a certificate issue. I have not experienced this problem before on any website when using Windows 10. (But yes, older versions of Windows can have similar problems to certificate problems)
Any ideas? I have not implemeted HTTP2 part of Windows API - is that a possible explanation? Would just be a bit odd to require that so.... But could possibly explain why Edge and not IE works.
I asked the website owner and the website was setup to only support TLS 1.3 and not accept TLS 1.2 --- TLS 1.3 support is still experimental in Windows 10 (internet options)

Is it possible to support TLSv1.3+ on Android API <20 by using a 3rd party library?

I have to support an Android device that uses Android API <20 (KitKat and older). We use AWS for our APIs and want to support TLSv1.3 and beyond, but these devices may not be upgraded for some time. Android API <20 doesn't natively support TLSv1.3+, but is it possible to use a third-party TLS library to support TLSv1.3? If so, how? Googling around has not turned up anything apart from "upgrade your device".
It's possible to do this using the Conscrypt Library which goes all the way back to Android 2.x
You can reference that library and then make use of it by:
Security.insertProviderAt(Conscrypt.newProvider(), 1);
I don't think Android device will support TLS 1.3 because TLS 1.3 is too new and almost all the browser cannot support TLS 1.3. The most of theme they use the older version TLS 1.2, TLS 1.2 compatible with all the IDE and Web platforms such as chrome or firefox. Also TLS 1.3 is very hard to create because there is almost no info about encryption with TLS 1.3.

Inno Setup Download plugin not able to download file due to TLS 1.1/1.2 issue

While i'm trying to download the file from Inno Setup download plugin, it fails with following error:
When explored more on this error I identified that enabling TLS 1.1 or TLS 1.2 from Internet Explorer settings it worked fine. But when I run the code in Windows XP or Windows Server 2003 (where it supports only TLS 1.0 so I cannot enable TLS 1.1 or TLS 1.2) it fails.
Code:
idpAddFile('https://www.testwebsite.com/downloads/SetupFiles.zip',
ExpandConstant('{tmp}\SetupFiles.zip'));
idpDownloadAfter(wpSelectDir);
TLS 1.1/1.2 is indeed not supported on Windows XP. Inno Download Plugin (IDP) is just a thin wrapper around Windows built-in implementation of HTTP. So no change in IDP code will allow TLS 1.2. You would have to implement HTTP and TLS from the scratch, what is an insane task.
Though note that the the problem about TLS version, not is not about certificate.
The only reasonable solution that supports Windows XP is enabling TLS 1.0 on the server.

IE11 on Windows Server 2012, not supporting common cipher methods?

We have an web app in Java for GlasFish server, we set cipher to TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 but IE11 wont open a page at all, saying we need to enalbe TLS 1.0, 1.1 and 1.2
These were enabled in Advanced settings but still no luck. Installed Chrome and it opened a page with no problem.
Trying to open the same page using IE11 from Windows 8.1 gave no problem, too.
Tried to disable Enhanced Security for IE on ser
Any hints, please?
Cipher support differs between browsers and operating systems and new ciphers also sometimes get added with patches. To get an overview which ciphers are probably supported by a specific system have a look at SSLLabs.
In any case it is recommended that you are using a set of secure ciphers to support the variety of systems and that you don't restrict yourself to a single cipher, especially an advanced and TLS 1.2 only cipher like the one you have chosen.