Red Hat DIRECTORY SERVER 8.1 - 11-01-2010 Manual de usuario descargar pdf (Pagina 53)

8.3. Encryption and decryption

Here comes the fun part – exchanging secret messages.

8.3.1. Encrypting a message

To encrypt a message, select the option Encrypt Message before sending, and

make sure the key icon in the lower right corner is lit. It is common practice to

also sign a message you're encrypting.

To send an encrypted message to someone, you need to have his public key. If

you have it, the key is automatically selected: Enigmail searches your keyring

and selects the public key that has an user ID that matches the recipient's

address. (Note: If you have set per-recipient rules, these will be looked up first.

You will learn about per-recipient rules in Section 8.6. )

This is done for each recipient. Recipient addresses are all those specified in

the mail headers To:, Cc:, and Bcc:.

Additionally, the message is also automatically encrypted with your own public

key, to allow you to read (from the Sent folder) the messages you sent. This

setting is regulated by the option OpenPGP → Preferences → Sending → Add

my own key to the recipients list, and we recommend you leave this option

checked.

As you see, this is pretty straightforward. But what happens if Enigmail is

unable to select a public key for a recipient, for instance because you don't

have it? In this case, Enigmail pops up the Key Selection window to ask you to

select the key(s) by hand:

In the figure, I was trying to send an encrypted email to

[email protected], which let's imagine is set as an alias and forwards

all mails to [email protected]. In this case, I would select John

1 2 ... 48 49 50 51 52 53 54 55 56 57 58 ... 105 106

Sin comentarios

Red Hat DIRECTORY SERVER 8.1 - 11-01-2010 Manual de usuario Pagina 53