The beauty of the simplicity of email encryption
The title sugest that email encryption is easy, and in a way, it is is.
The internet is not secure
Email is, by design, not secure. It is a simple text message sent on a computer network. Originally, the network itself was like a phone line, anybody who had access to it could copy and read the data. It is still the case. Therefore new features were introduced to make the communication more secure. The network itself is still not secure, but the data sent on the network is. Protocols like ssh and https send the data encrypted, therefore even if somebody has access to the network, the data they can read doesnât make sense.
Something similar happened in email. The network it uses is the same, the email itself is the same, but there is way to send the email encrypted.
One big issue is that to do so, you need your own infrastructure. Reason is that the encryption happens on the service level, the mail server itself creates the encrypted channel to send the message.
Just a little more details what this means
In case of ssh, you have your own private encryption keys, and you install the public parts on servers you have access to. This is a very individual approach, and it needs resources only from you. You are the one who maintain your own keys. This obviously canât work for email, you canât install your public key on everybodyâs devices where you send email. There is a solution that does this exactly, but it is not convenient.
The public/private key infrastructure is used in case of https too. Contrary to the marketing which successfully convinced many to pay thousands per year to buy fancy certificates, https encryption is nothing more than encrypting the communication. Well, it was used to provide authenticity, but it was a mistake. When a root certificate was stolen, many fake site could claim it was authentic, becasue authenticity based on the signature of the owner of the root certificate. Letsencrypt is a more open approach and it does what https is for: it tells you that you comminucate with the domain itself and encrypts the communication. It is possible in this case, because there is an infrastructure behind the encryption certificates that is used by the browsers to verifiy the keys. This wouldnât be convenient for individual email accounts either.
We have email encryption already
However, it works on the server side. When you send an email, your email client contacts the server which manages your email address. The client can be browser based or a program, it doesnât matter. So the client contacts the server, and it is actually the server that sends your email, not you. The server contacts the server of the recipient email account, and sends over the message. Then the recipient use their client program to download or access the email. The encryption can happen between the two servers. That is the phase when the message is in a public space. It can happen, becasue it is not encrypted by default. The same certificates that are used for https can be used here, therefore server admins very easily can have Letsencrypt certificates to be used on mail servers. If it is done, the message sent encrypted on the public network automatically. Only condition is that both servers have to be configured for TLS. This means that if you and the recipient have control over the email server, and both of you use TLS, the email is actually encrypted and can be read only by you.
Only you need your own server
Which sounds scarier than it is. It is very easy to have and maintain your own mail server, you only need a Virtual Private Server which has a properly configured mail server and that is all.
Yes, you can rent one from us :). We offer an easy to use interface for maintenance. Even if you donât know exactly how it works, it does most of the work for you.