TLS

Overview

NOTE: TLS is the sucessor to the more known SSL. SSL was deprecated in 2015 and now only TLS is/should be used.

TLS, short for Transport Layer Security is a cryptographic protocol that is designed to provide secure connections over a network. This not only means more privacy for both ends but also better data integrity because it can be verified that the sent data was not tampered with. (Man-In-The-Middle Attack)

This means that data that is being sent over the network is completely confidental and contains only the data that was initially sent, even if the whole network was compromized, e.g. an attacker has complete control over the network.

Certificate Authority

What is this?

In the context of TLS, a certificate authority refers to an entity that stores, signs and issues digital certificates. If both application a and application b cannot trust each other, they need a third-party that both can agree on trusting. This is a certificate authority.

NOTE: Any site that uses self-signed certificates acts as its own CA.

Who trusts who generally differs a bit with Mozilla Firefox trusting ~50 organizations that provide ~150 root certificates. MacOS trusts ~60 organizations that provide ~170 root certificates and lastly Microsoft Windows trusts ~101 organizations that provide ~250 root certificates. Same goes with Android.

What does it do?

A CA signs a public key of somebody, basically telling every browser that this person actually owns this domain and isn’t faking something. For example: Adam wants to have his domain example.com verified. He first creates a certificate using something like:

# Generate an RSA private key
openssl genpkey -algorithm RSA -pkeyopt rsa_keygen_bits:4096 -out private_key
openssl req -new -sha256 -key private_key -out request

Then he can upload this to a CA, which will digitally sign this. A client can then verify that this was actually signed by the CA with some crazy math. Adam then needs to verify that he actually owns this domain by, for example, replying to a email that was sent to webmaster@example.com. This is called domain validation (DV). There are also other ways to confirm that Adam is who he says he is, however those are more used in professional contexts. Namely they are organization validated (OV) and extended validation (EV). Both require some additional information to verify that the business is who they say they are, for example, physical address, type and status. Some browsers will display a green indicator in the url bar when a EV is used instead of an OV.

NOTE: Many end-users do not recognize any difference between EV, OV and DV. Additionally a test using Internet Explorer 7 in 2009 showed that users did not care if the domain had an DV, OV or EV. (Green url bar)

NOTE: The past showed that DV has some severe limitations. For example, some mail providers didn’t block ssladmin@example.com, which some CA’s used to verify the domain ownership. This means that if somebody registered this mail and tried to take over the domain, he didn’t even need access to the admin email to trick browsers to trust their new website. In November 2011 somebody actually used this method to gain a DV vor live.fi even though he was not the domain owner. live.fi was the finnish version of Microsoft Live.

Sources