Just stumbled over «The Illustrated TLS 1.2 Connection» (again).

You can easily see the different messages and hover over the byte ranges to get a short explanation. Or click on the «Annotations» button to see details about each of the field.

What a great resource by #MichaelDriscoll!

1/6
#TLS #TLS12 #Illustrated
https://tls12.xargs.org/

The Illustrated TLS 1.2 Connection

Every byte of a TLS connection explained and reproduced

Scheint nicht die Ursache zu sein, auf einem Windows 2016 läuft die Kommunikation trotzdem, obwohl der auch max. #TLS12 unterstützt. Ist wohl irgendwas an diesem einen Client.
Hat jemand eine Idee, ob man #Windows 8.1 noch #TLS13 beibringen kann? Offiziell ist bei #TLS12 Schluss #computerkram
Encryption is on the Rise!

The migration from TLS 1.2 to 1.3 has some very specific drivers and restraints. Cisco worked with research and consulting firm EMA to survey the market regarding why they have or have not embraced TLS 1.3 at this point.

Cisco Blogs
The TLS Handshake Explained [A Layman’s Guide] - InfoSec Insights

A TLS handshake is how two entities introduce themselves in order to verify one or both digital identities & establish a secure connection.

InfoSec Insights

I encountered this #powershell issue a bit too often, so I decided to do some research. Does powershell fail your install-module or find-packageprovider commands, complaining it's unable to download, while you can access the internet just fine? It may be because the #PowershellGallery updated their #securitycipher to #TLS12:

https://medium.com/@aev_software/get-powershell-nuget-to-install-modules-if-it-complains-its-offline-set-better-tls-cipher-version-10eaa7300823

Get Powershell NuGet to install modules if it complains it’s offline: set a better TLS cipher version

Did Powershell choose an internet security cipher that is outdated or not available? It did on my Windows Server 2012 R2. Assuming your Microsoft Windows computing device is online and can get…

Medium
@danyork After a recent #SSL error using a legacy browser, I have been looking into #TLS implementation and why so few sites actually have #TLS13 given that it has been out since 2016. Those that have it usually downgrade to #TLS12 if the browser doesn't support 1.3. Why are so few sites using this new "standard" and why are those that do not enforcing it? I assume that 1.2 (which is from 2008) is still secure enough for banking, secure email, etc. Any insights?