'def title How to encrypt email 'def desc For PGP add keys in your client. For S/MIME another article is linked. Also contains a comparison of a lot of mail clients. # {title} {pagenav 5 min;16 September 2022;16 November 2022} :contents :numbered 1. {uhref Getting keys} :numbered 1. {uhref PGP} .numbered 1. {uhref pgptool.org} 2. {uhref GNU Privacy Guard} 2. {uhref S/MIME} 2. {uhref Exchanging keys} 3. {uhref Configuring clients} In {url this;/blog/encrypted-email} blog post I shared the most common technologies for email encryption and a bit of how they work. PGP and S/MIME are the most popular schemes, with support from a lot of clients. These are all the steps required to go from having no encryption, to encrypting all of your future emails. ## Getting keys PGP and S/MIME are both built upon {url 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 As {url discussed;/blog/encrypted-email/#pgp}, PGP relies on a {url web of trust;https://en.wikipedia.org/wiki/Web_of_trust}, meaning you can generate your keys by yourself. #### pgptool.org By far, the easiest way to do this is via the website {url 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 As an alternative, you can use a desktop program. The most popular one is {url GNU Privacy Guard;https://www.gnupg.org/} (GPG for short). It is {url available;https://gnupg.org/download/#binary} on most desktop operating systems, including {url Windows;https://gpg4win.org/download.html} and {url MacOS;https://gpgtools.org/}. The {i Windows} version comes with a graphical user interface, so it's easiest to use that: :ordered 1. Open the application "Kleopatra" 2. Click on {` File} -> {` New Certificate} 3. Input your details and press {` OK} .bulleted - Feel free to click on {` Advanced Settings} and look if if the value for {` RSA} is {` 4096 bit}, the value for {` + RSA} is enabled and is {` 4096 bits}, and finally both {` Signing} and {` Authentication} are selected 4. On the next screen, press {` Create} 5. You'll be asked for a password. Make one up, and enter it, but do not forget it! .bulleted - The password is used for your private key. If anyone gets ahold if it, they {b will} be able to impersonate you. A password makes sure that doesn't happen, at least until you tell everyone that your key was leaked. 6. On the final screen, click {` Finish} 7. To help with the next chapter, we'll extract your public key. In "Kleopatra" you should see a line, containing your name and email. Right-click on it, and select {` Export Certificate}. On {i Linux} and {i MacOS}, you can use the command line: :ordered 1. Enter this command in your favorite terminal ```bash gpg --full-generate-key 2. Follow the prompt on the screen (sample pictures available in {url encryptionconsulting.com;https://www.encryptionconsulting.com/how-to-generate-pgp-key-pair/}) 3. Export your public key (of course, change me@email.com and the location to the one you want, but don't forget the .asc extension) ```bash gpg --armor --export me@email.com > ~/Documents/me-email.com-publickey.asc ### S/MIME Contrary to PGP, S/MIME relies on a certificate authority, meaning you'll have to buy your keys from someone. Any provider from {url 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 {url Actalis;https://www.actalis.com/s-mime-certificates.aspx}. Their process is pretty straight forward, just follow the instructions (shown in {url this;https://www.dannyguo.com/blog/how-to-get-a-free-s-mime-certificate/} article). ## 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 public key. It doesn't matter how you do that, even if it's with unencrypted emails. Remember, {b never} send your {b private} key to anyone! ## 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. When writing a message, don't forget to check if encryption is turned on for this email! On most clients, in the compose window, you'll have to select an option to enable encryption, but others do that automatically. {i Freemium means it has a free and a paid tier. Premium means you have to pay for it. FOSS means it's free and open source. FreemiumOSS means it is free and open source, but also has paid tiers.} :table :6 'def 1 {^ {url 1;#1}} 'def 2 {^ {url 2;#2}} 'def 3 {^ {url 3;#3}} 'def * {^ {url *;#*}} |= Client |= Type |= Platform |= PGP/Inline |= PGP/MIME |= S/MIME |= Web |: |: |: |: |: |: Gmail |: Freemium |: Web |: {url Yes;https://flowcrypt.com/}{1} |: {url Yes;https://flowcrypt.com/}{1} |: {url Yes;https://support.google.com/a/answer/6374496?hl=en&ref_topic=9061730}{2} |: Outlook |: Freemium |: Web |: No |: No |: {url Yes;https:://support.microsoft.com/en-us/office/encrypt-email-messages-373339cb-bf1a-4509-b296-802a39d801dc#bkmk_encryptwithsmime}{2} |: iCloud mail |: Freemium |: Web |: {url Yes;https://support.apple.com/en-us/HT201214} |: {url Yes;https://support.apple.com/en-us/HT201214} |: {url Yes;https://support.apple.com/en-us/HT202345} |: Yahoo! |: Freemium |: Web |: No |: No |: No |: Protonmail |: Freemium |: Web |: {url Yes;https://proton.me/support/how-to-use-pgp} |: {url Yes;https://proton.me/support/how-to-use-pgp} |: No |: Roundcube |: Self-hosted |: Web |: {url Yes;https://github.com/roundcube/roundcubemail/tree/master/plugins/enigma}{1} |: {url Yes;https://github.com/roundcube/roundcubemail/tree/master/plugins/enigma}{1} |: {url No;https://github.com/roundcube/roundcubemail/issues/4977} |: Rainloop |: Self-hosted |: Web |: Yes |: {url No;https://github.com/RainLoop/rainloop-webmail/issues/1798} |: No |= Desktop |: |: |: |: |: |: Thunderbird |: FOSS |: Windows, MacOS, Linux |: {url Yes;https://support.mozilla.org/en-US/kb/openpgp-thunderbird-howto-and-faq#w_i-have-never-used-openpgp-with-thunderbird-before-how-do-i-setup-openpgp} |: {url Yes;https://support.mozilla.org/en-US/kb/openpgp-thunderbird-howto-and-faq#w_i-have-never-used-openpgp-with-thunderbird-before-how-do-i-setup-openpgp} |: {url Yes;https://support.mozilla.org/en-US/kb/openpgp-thunderbird-howto-and-faq} |: Outlook |: Premium |: Windows, MacOS |: No |: No |: {url Yes;https://support.microsoft.com/en-us/office/encrypt-email-messages-373339cb-bf1a-4509-b296-802a39d801dc#bkmk_encryptwithsmime} |: Mailbird |: Premium |: Windows |: {url No;https://mailbird.featureupvote.com/suggestions/74494/pgp-encryption-support} |: {url No;https://mailbird.featureupvote.com/suggestions/74494/pgp-encryption-support} |: {url No;https://mailbird.featureupvote.com/suggestions/160861/smime-support} |: Evolution |: FOSS |: Linux |: {url Yes;https://help.gnome.org/users/evolution/stable/mail-encryption-gpg-set-up.html.en} |: {url Yes;https://help.gnome.org/users/evolution/stable/mail-encryption-gpg-set-up.html.en} |: {url Yes;https://help.gnome.org/users/evolution/stable/mail-encryption-s-mime-manage.html.en} |: Sylpheed |: FOSS |: Windows, MacOS, Linux |: {url Yes;https://sylpheed.sraoss.jp/doc/manual/en/sylpheed-8.html#ss8.2} |: {url Yes;https://sylpheed.sraoss.jp/doc/manual/en/sylpheed-8.html#ss8.2} |: {url No;https://www.sraoss.jp/pipermail/sylpheed/2011-May/004551.html} |: Claws-mail |: FOSS |: Windows, Linux |: {url Yes;https://claws-mail.org/plugin.:php?plugin=gpg}{1} |: {url Yes;https://claws-mail.org/plugin.php?plugin=gpg}{1} |: {url Yes;https://claws-mail.org/plugins.php}{1} |= Mobile |: |: |: |: |: |: Gmail |: Free |: Android, iOS |: No |: No |: Yes{3} |: Outlook |: Free |: Android, iOS |: No |: No |: Yes{3} |: Apple Mail |: Free |: iOS |: Yes |: Yes |: Yes |: Yahoo! |: Free |: Android, iOS |: No |: No |: No |: Edison |: Free |: Android, iOS |: No |: No |: No |: Protonmail |: Free |: Android, iOS |: {url Yes;https://proton.me/support/how-to-use-pgp} |: {url Yes;https://proton.me/support/how-to-use-pgp} |: No |: K-9 Mail |: FOSS |: Android |: {url Yes;https://docs.k9mail.app/en/current/security/pgp/} |: {url Yes;https://docs.k9mail.app/en/current/security/pgp/} |: {url No;https://docs.k9mail.app/en/current/security/overview/#end-to-end-encryption} |: FairEmail |: FreemiumOSS |: Android |: {url Yes;https://github.com/M66B/FairEmail/blob/master/FAQ.md} |: {url Yes;https://github.com/M66B/FairEmail/blob/master/FAQ.md} |: {url Yes;https://github.com/M66B/FairEmail/blob/master/FAQ.md}{*} {^ 1} Available with an extension/plugin{br} {^ 2} Available in a paid version of the software (assuming the software is Freemium; this is true for all Premium software){br} {^ 3} Available with a Premium account (even if the software is Free){br} {^ *} You can read S/MIME messages, but signing and encrypting is a pro feature 'def 1 'def 2 'def 3