25.02.2013 Views

TCP/IP Tutorial and Technical Overview - IBM Redbooks

TCP/IP Tutorial and Technical Overview - IBM Redbooks

TCP/IP Tutorial and Technical Overview - 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.

public key <strong>and</strong> identification, a digital certificate usually contains other<br />

information too, such as:<br />

► Date of issue<br />

► Expiration date<br />

► Miscellaneous information from the issuing CA (for example, serial number)<br />

Note: There is an international st<strong>and</strong>ard in place for digital certificates: The<br />

ISO X.509 protocols.<br />

The parties retrieve each other's digital certificate <strong>and</strong> authenticate it using the<br />

public key of the issuing certification authority. They have confidence that the<br />

public keys are real, because a trusted third party vouches for them. This helps<br />

protect against both man-in-the-middle <strong>and</strong> impersonation attacks.<br />

It is easy to imagine that one CA cannot cover all needs. What happens when<br />

Bob's certificate is issued by a CA unknown to Alice? Can she trust that unknown<br />

authority? Well, this is entirely her decision, but to make life easier, CAs can form<br />

a hierarchy, often referred to as the trust chain. Each member in the chain has a<br />

certificate signed by its superior authority. The higher the CA is in the chain, the<br />

tighter security procedures are in place. The root CA is trusted by everyone <strong>and</strong><br />

its private key is top secret.<br />

Alice can traverse the chain upward until she finds a CA that she trusts. The<br />

traversal consists of verifying the subordinate CA's public key <strong>and</strong> identity using<br />

the certificate issued to it by the superior CA.<br />

When a trusted CA is found in the chain, Alice is assured that Bob's issuing CA is<br />

trustworthy. This is all about delegation of trust. We trust your identity card if<br />

somebody who we trust signs it. And if the signer is unknown to us, we can go<br />

upward <strong>and</strong> see who signs for the signer, <strong>and</strong> so on.<br />

An implementation of this concept is in the SET protocol, where the major credit<br />

card br<strong>and</strong>s operate their own CA hierarchies that converge to a common root.<br />

Lotus® Notes® authentication, as another example, is also based on certificates,<br />

<strong>and</strong> it can be implemented using hierarchical trust chains. PGP also uses a<br />

similar approach, but its trust chain is based on persons <strong>and</strong> it is a distributed<br />

Web rather than a strict hierarchical tree.<br />

22.2.6 R<strong>and</strong>om-number generators<br />

An important component of a cryptosystem is the r<strong>and</strong>om-number generator.<br />

Many times r<strong>and</strong>om session keys <strong>and</strong> r<strong>and</strong>om initialization variables (often<br />

referred to as initialization vectors) are generated. For example, DES requires an<br />

792 <strong>TCP</strong>/<strong>IP</strong> <strong>Tutorial</strong> <strong>and</strong> <strong>Technical</strong> <strong>Overview</strong>

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

Saved successfully!

Ooh no, something went wrong!