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.

connection. A good solution is to use SSL, which we will explore in the next<br />

section.<br />

6.2.5 Secure Sockets Layer<br />

As we’ve already said a couple of times, authentication is an attempt to address<br />

two of our primary security objectives, namely: access control and identity<br />

verification. Regrettably, authentication does not address our other primary<br />

security objectives, namely: confidentiality and data integrity.<br />

Worse even, authentication is not truly secure because passwords are sent over<br />

a network in a form close to plaintext – they’re Base64 encoded. The emphasis<br />

here is on “encoded”, not “encrypted.” Base64 is an encoding algorithm, not<br />

encryption, and as such it's supposed to be easily reversible. Thus, given that<br />

passwords are generally transmitted within HTTP headers, if these are<br />

intercepted (using a packet sniffer, for example), they can be easily decoded and<br />

used by impersonators.<br />

Thus, a protocol that uses cryptographic techniques is needed. There are<br />

several protocols that seek to meet this need, but only one is universally<br />

implemented: Secure Sockets Layer (SSL).<br />

SSL is widely used on the Internet not only in conjunction with HTTP, but also<br />

with a number of other popular application protocols, specifically LDAP, POP3,<br />

HTTP, SMTP, IIOP, or IMAP.<br />

What is SSL?<br />

The Secure Sockets Layer protocol was originally created by Netscape Inc., but<br />

now it is implemented in most Internet-based client/server software. SSL makes<br />

use of a number of cryptographic techniques, such as public key and symmetric<br />

key encryption, digital signatures, and public key certificates.<br />

Note: The current version of SSL is 3.0, however, it has been supplanted by<br />

the new Transport Layer Security (TLS), an IETF standard protocol. TLS was<br />

first defined in RFC 2246: “The TLS Protocol Version 1.0". Since there is no<br />

support in Notes and Domino for TLS -- and there aren’t any plans to support<br />

TLS in the foreseeable future, this chapter only <strong>cover</strong>s SSL v3.<br />

SSL version 3.0, which was introduced in 1996, is a security protocol that:<br />

► Encrypts information sent over the network from client and server, providing<br />

confidentiality<br />

► Validates that the message sent to a recipient was not tampered with,<br />

providing data integrity<br />

Chapter 6. Public key infrastructures 249

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

Saved successfully!

Ooh no, something went wrong!