Red Hat DIRECTORY SERVER 8.1 - 11-01-2010 Instrukcja Użytkownika Pobierz pdf (Strona 59)

8.4. Handling attachments

When sending an encrypted or signed email message that has attachments,

you will be given the choice how to encrypt/sign the attachments:

There are three mutually exclusive options:

• Just encrypt/sign the message text, but not the attachments. This will

only protect the message text.

• Encrypt/sign each attachment separately and send the message using

inline PGP. In this case, the signature for each attachment

filename.ext will be stored in an additional attached file

filename.ext.sig. If the attachment must be encrypted, it will be

renamed as filename.ext.pgp. This is the default option, which is

also the safest and most recommended.

• Encrypt/sign the message as a whole and send it using PGP/MIME. As

said previously, the PGP/MIME standard is not supported by all mail

clients, so the risk here is that the recipient could be unable to read the

message.

If you tick the option Use the selected method for all future attachments,

Enigmail will remember your choice and won't ask you any more. To have

Enigmail show you the options again, go to OpenPGP → Preferences →

Advanced and click on the Reset Warnings button.

When you receive an encrypted attachment, you can view it or save it simply by

right-clicking on it and selecting, respectively, Decrypt and Open or Decrypt and

Save As....

1 2 ... 54 55 56 57 58 59 60 61 62 63 64 ... 105 106

Brak uwag

Red Hat DIRECTORY SERVER 8.1 - 11-01-2010 Instrukcja Użytkownika Strona 59