22.12.2012 Views

Front cover - IBM Redbooks

Front cover - IBM Redbooks

Front cover - IBM Redbooks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

270 Lotus Security Handbook<br />

encryption key (the secret key, which is generally referred to as being a<br />

session key, since a new random key is generated every time an encrypted<br />

S/MIME message is sent) and encrypts the message with it.<br />

2. The session encryption key is encrypted (using either Triple-DES or RC2)<br />

with the recipient’s public key and attached to the message, which means that<br />

only Bob’s RSA public key will be able to decrypt it.<br />

3. The encrypted text and the encrypted key are sent to Bob via SMTP.<br />

4. Bob’s messaging client uses Bob’s RSA private key to decrypt the encrypted<br />

key (again, using RC2) and gets a decrypted session key. Here, secrecy is<br />

guaranteed, because only Bob's private key can be used to decrypt the<br />

session key needed to decrypt the message.<br />

5. Bob’s messaging client uses the decrypted session key to decrypt the mail<br />

message (using either Triple-DES or RC2, depending on which algorithm it<br />

was encrypted with), resulting in the decrypted, original message that was<br />

sent by Alice.<br />

If Bob’s messaging client is unable to decrypt the e-mail sent by Alice, this is<br />

probably because Bob has gotten a new X.509 certificate and the public key in<br />

the directory Alice has access to is the old key.<br />

Looking at the process shown in Figure 6-26, this is in effect a technique in<br />

S/MIME often referred to as a “digital envelope,” whereby the message is actually<br />

encrypted using the shorter symmetric cipher and the symmetric cipher is then<br />

encrypted using the larger asymmetric key, and sent along with the encrypted<br />

message.<br />

This method is preferred because it is far quicker to encrypt the whole message<br />

using the shorter symmetric key than to encrypt the message using the longer<br />

asymmetric key. The message is still quite safe, since this approach combines<br />

the speed of symmetric encryption with the security of asymmetric encryption.<br />

Tamper detection<br />

For tamper detection, or data integrity, S/MIME provides assurance that the<br />

message can be properly validated, meaning that the message was not<br />

tampered with during transit. This utilizes a technique known a digital signatures<br />

and works in a similar manner to what we already discussed in Notes<br />

messaging.<br />

Signing: Authenticating the sender with Digital Signatures<br />

S/MIME provides message signing through the use of digital signatures, which<br />

permits the authentication of the message (confirming that the person who sent it<br />

is indeed the sender) as well as tamper detection (that the message itself is<br />

original and not a single bit of it was modified). This is illustrated in Figure 6-27.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!