diff options
[src] Removed manually placed heading anchors in all pages
1 files changed, 0 insertions, 8 deletions
| -rw-r--r-- | src/tutorials/how-to-encrypt-email/index.md | 8 |
diff --git a/src/tutorials/how-to-encrypt-email/index.md b/src/tutorials/how-to-encrypt-email/index.md index 0b1d957..0fe206a 100644 --- a/src/tutorials/how-to-encrypt-email/index.md +++ b/src/tutorials/how-to-encrypt-email/index.md @@ -11,7 +11,6 @@ In [this](/blog/encrypted-email) blog post I shared the most common technologies These are all the steps required to go from having no encryption, to encrypting all of your future emails. ## Contents -<div></div> 1. [Getting keys](#getting-keys) 1. [PGP](#pgp) @@ -22,22 +21,18 @@ These are all the steps required to go from having no encryption, to encrypting 3. [Configuring clients](#configuring-clients) ## Getting keys -[](#getting-keys) PGP and S/MIME are both built upon [public-key cryptography](https://en.wikipedia.org/wiki/Public-key_cryptography) so you and all of your recipients need to have a pair of public and private keys. ### PGP -[](#pgp) As [discussed](/blog/encrypted-email/#pgp), PGP relies on a [web of trust](https://en.wikipedia.org/wiki/Web_of_trust), meaning you can generate your keys by yourself. #### pgptool.org -[](#pgptool.org) By far, the easiest way to do this is via the website [pgptool.org](https://pgptool.org/). Just open the link, fill out your details, select the recommended values (select never as your expiration time) and wait a couple minutes. After they are done, you can click the two red buttons to download your public and private keys. #### GNU Privacy Guard -[](#gnu-privacy-guard) As an alternative, you can use a desktop program. The most popular one is [GNU Privacy Guard](https://www.gnupg.org/) (GPG for short). It is [available](https://gnupg.org/download/#binary) on most desktop operating systems, including [Windows](https://gpg4win.org/download.html) and [MacOS](https://gpgtools.org/). @@ -68,19 +63,16 @@ On *Linux* and *MacOS*, you can use the command line: ``` ### S/MIME -[](#smime) Contrary to PGP, S/MIME relies on a certificate authority, meaning you'll have to buy your keys from someone. Any provider from [Google](https://support.google.com/a/answer/7448393?hl=en&ref_topic=9061730)'s list of trusted CAs will work. Currently, the only one that provides free certificates is [Actalis](https://www.actalis.com/s-mime-certificates.aspx). Their process is pretty straight forward, just follow the instructions (shown in [this](https://www.dannyguo.com/blog/how-to-get-a-free-s-mime-certificate/) article). ## Exchanging keys -[](#exchanging-keys) You should now have a text file with your public key in it. When you want to send an encrypted email to someone, ask them for their public key, and meanwhile send them your private key. It doesn't matter how you do that, even if it's with unencrypted emails. ## Configuring clients -[](#configuring-clients) Now we need to configure your email application to automatically encrypt and decrypt messages. There are a lot of email clients, so I have compiled the most used ones and linked resources on how to set them up. |