HOME Authentication instances Top 13 Signing e-mails12 Encrypting e-mails Contents German

12 Encrypting e-mails

Now it is getting exciting again: You are sending an encrypted e-mail.

In this case, you will need Outlook (or another e-mail program that supports cryptography), Kleopatra and of course the public certificate of the person you are correspondign with.

Note for OpenPGP:

You can use Adele to practice the encryption process with OpenPGP; on the other hand, Adele does not support S/MIME. You can send the e-mail to be encrypted to adele@gnupp.de. It does not matter what your write in your message, since Adele cannot read it.

Note for S/MIMIE:

Following the installation of Gpg4win, the S/MIME functionality is already activated in GpgOL. If you want to turn off S/MIME (with GnuPG), for example to use Outlook's own S/MIME function, you have to deactivate the option Activate S/MIME support in the following GpgOL option dialog under Extras -> Options -> GpgOL:

Send an encrypted message

First, compose a new in Outlook and address it to the person you are writing to.

To send your message as in an encrypted form, select the item Extras -> Encrypt message in the menu of the message window. The button with the lock icon in the tool bar is activated - you can also click right on the lock.

Your Outlook message windows should look something like this:

Now click [Send].

 
Gpg4win will automatically detect the protocol - OpenPGP or S/MIME - of the public certificate provided by the person you are corresponding with.

As long as there is only one certificate that matches the recipient's e-mail address, your message will be encrypted and sent.

Selecting certificates

If Kleopatra is not able to clearly determine a recipient certificate using the le-mail address, e.g. if you have an OpenPGP and S/MIME certificate from the person you are corresponding with, a selection dialog which allows you to select the right certificate will be displayed.

If Kleopatra is not able to find the public certificate of the person you are corresponding with, you probably have not imported it into your certificate administration yet (see Chapter 10) or perhaps have not authenticated it yet (for OpenPGP; see Chapter 11), or have not expressed your trust in the root certificate of the certification chain (for S/MIME, see Chapter 22.7).

You need the correct public certificate of your correspondence partner to encrypt your messages.

Remember the principle in Chapter 3:

You have to use someone's public certificate to send them an an encrypted e-mail.

Completing the encryption process

Once your message was successfully encrypted and sent, you will receive a confirmation message:

Congratulations! You have encrypted your first e-mail!


© 2nd August 2013, v3.0.0
The Gpg4win Compendium is filed under the GNU Free Documentation License v1.2.


HOME Authentication instances Top 13 Signing e-mails12 Encrypting e-mails Contents German