This protocol evolved, with TLS v1.1 in 2006 and TLS 1.2 in August 2008. There was another protocol lingering around since 1999, called Transport Layer Security (TLS), and was intended as an upgrade from SSLv3. The reason for that can be found in the RFC document, section 4 which is aptly titled " SSLv3 is Comprehensively Broken". This protocol lasted until 2015 when it was officially deprecated by the Internet Engineering Task Force IETF (see RFC 7568). It was officially released in 1995 (version 2.0), and its final version (v3.0) was available at the end of 1996. In 1994, Netscape introduced the Secure Sockets Layer (SSL) protocol to address this. In this case, you will have to submit your payment details to the retailer and you will want to keep that communication confidential for obvious reasons. For example, when you want to buy an item online. In some cases, the communication needs to be secured from prying eyes. Allowing a mobile app to communicate with an API Backend.Allowing a browser to load and display content from a remote server.
TCP is the building block used by many other higher-level protocols (such as HTTP) to provide end-users with common capabilities such as:
To begin, let's travel back to the fabulous 1990s, a decade that saw the fall of the Soviet Union, many great music masterpieces 🤘 and last but not least the stratospheric rise of the Internet.Īs more and more people started using it, a need for securing communications happening over the TCP protocol arose. We start here discussing TLS 1.2 - You can find Part 2 here.
This article is the first of a series focusing on TLS 1.2 and TLS 1.3. Let's use some of the time for this Coronavirus lockdown productively, and gain an overall view of the modern Transport Layer Security (TLS) landscape. I've been spending quite some time talking about optimal TLS set up in the past.
0 kommentar(er)
