But consumers and smaller businesses seem to think that adding extra security isn’t worth the extra work required. The problem with this take is anyone who refuses to take the extra steps might find themselves on the wrong end of a data breach. You might have sent some sensitive information in an innocent email, only to find some bad actor intercepted the message and was able to easily read the content of that email and extract the information. You don’t want that. Even if it does require an extra bit of work on your part, being safe is much better than being sorry. So what do you do? You encrypt your email (or the email containing sensitive information).
1. Generate a key pair
I’ll be demonstrating on Pop!_OS Linux, but this will work the same way on any platform that supports GnuPG (Linux and macOS). For the Windows OS, you’ll need to use Gpg4win.
The recipient creates a GPG key pair (consisting of a public and a private key) and sends the public key to you.You import the public key into your keyring.You then send a message to the recipient’s email address (associated with the newly-imported key).The recipient receives the email and can read it because they have the private key that matches the public key you imported.
If the email is intercepted on the way, it cannot be read without the matching private key. That, of course, brings up one crucial issue that cannot be stressed enough – never share your private key with anyone. Yes, adding encryption to email does add extra steps to your process, but when dealing with sensitive information, those extra steps will be well worth the effort. Here’s how it works. To generate a keypair, open a terminal window and issue the command: You’ll be asked the following questions (answer with the defaults):
Please select what kind of key you want:What keysize do you want?Key is valid for?
When prompted, type y to verify the creation of the key. You’ll then be required to add a real name, an email address associated with the key, and an optional comment. Finally, you’ll be required to type and verify a password for the new key pair. After that, your key is created and ready for export.
2. Export the public key
Next, we need to export the public key so it can then be sent to the person who will need to send you an encrypted email. To export the key, issue the command: Where EMAIL is the email associated with the key you just generated. Once you’ve generated the file (named public_key), send it to the person who will be encrypting the email to you.
3. Importing a public key
Next, we need to import the public key that was sent to you. Open Thunderbird, click the Menu button and click Account Settings. In the left sidebar, click End-To-End Encryption and then click OpenPGP Key Manager (Figure 1). Click File > Import Public Key From File, and then make sure to select All Files from the drop-down at the bottom right corner of the window (Figure 2). Gaining access to the OpenPGP manager from within Thunderbird. Locate the file you saved (the public key from the recipient that will receive your email) and click Open. In the resulting window (Figure 3), select Accepted (unverified) and click OK. Importing the public key from within the OpenPGP Key Manager. Click OK, and the key will be imported and ready to use. Importing Henry Jekyll’s key might not be the best idea, but I’m going for it.
4. How to encrypt an email
Close the Key Manager and go back to the Thunderbird main window. Compose a new message to the email address associated with the encryption key, and then (in the email compose window) click the Security drop-down and click the checkboxes for Require Encryption and Digitally Sign This Message (Figure 4). Send the message as normal, and it will be encrypted such that the only person that can decrypt it is the owner of the private key that matches the public key you imported. Encrypting and signing your new email. And that, my dear friends, is how email encryption works. I hope you find this to be much easier than you expect and will inspire you to start using this extra security layer in your email communications.
