PGP & Smime
PGP & Smime
Layer:
PGP and S/MIME
16.1
Chapter 16
Objectives
To explain the general structure of an e-mail
application program
To d i sc uss how P GP c an p rov i d e se c uri ty
s e r v i c e s
for e-mail
To discuss how S/MIME can provide security
services for e-mail
To def in e trust mechanism in both PGP and
S/MIME
To show the structure of messages exchanged in
PGP and S/MIME
16.2
16-1 E-MAIL
16.3
16.1.1 E-mail Architecture
16.4
16.1.2 E-mail Security
Cryptographic Algorithms
Note
In e-mail security, the sender of the message
needs to include the name or identifiers
of the algorithms used in the message.
Certificates
It is obvious that some public-key algorithms must
be used for e-mail security.
16.5
16.1.2 Continued
Cryptographic Secrets
Note
In e-mail security, the encryption/decryption is
done using a symmetric-key algorithm,
but the secret key to decrypt the message is
encrypted with the public key of the
receiver and is sent with the message.
16.6
16-2 PGP
16.8
16.2.1 Continued
Message Integrity
16.9
16.2.1 Continued
Compression
16.10
16.2.1 Continued
Conf id entiality with One-Time Session
Key
16.11
16.2.1 Continued
Code Conversion
Another service provided by PGP is code
conversion. PGP uses Radix-64 conversion.
Segmentation
PGP allows segmentation of the message.
16.12
16.2.2 Key Rings
16.13
16.2.3 PGP Certificates
X.509 Certificates
Protocols that use X.509 certif icates depend on
the hierarchical structure of the trust.
Note
In X.509, there is a single path from the fully
trusted authority to any certificate.
16.14
16.2.3 Continued
PGP Certificates
In PGP, there is no need for CAs; anyone in the ring
can sign a certificate for anyone else in the ring.
Note
In PGP, there can be multiple paths from fully or
partially trusted authorities to any subject.
16.16
16.2.3 Continued
16.17
16.2.5 Extracting Information from Rings
Figure 16.10 Extracting information at the sender site
16.18
16.2.5 Continued
Figure 16.11 Extracting information at the receiver site
16.19
16-3 S/MIME
16.20
16.3.1 Continued
16.21
16.3.1 Continued
16.22
16.3.1 Continued
MIME-Version
This header defines the version of MIME used. The
current version is 1.1.
Content-Type
The content type and the content subtype are
separated by a slash. Depending on the subtype,
the header may contain other parameters.
16.23
16.3.1 Continued
16.24
16.3.1 Continued
16.25
16.3.2 S/MIME
16.27
16.3.2 Continued
Figure 16.28 Enveloped-data content type( for privacy)
16.28
16.3.2 Continued
Figure 16.29 Digest-data content type ( for integrity
of data, used as content for Enveloped Data content
type)
16.29
16.3.2 Continued
Figure 16.30 Authenticated-data content type
16.30
16.3.2 Continued
Cryptographic Algorithms
S/MIME def ines several cryptographic algorithms.
The term “must” means an absolute requirement;
the term “should” means recommendation.
16.31