ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzain_5.4.0.1/rzainrzaintls.htm

132 lines
7.7 KiB
HTML

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="en-us" xml:lang="en-us">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="security" content="public" />
<meta name="Robots" content="index,follow" />
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta name="DC.Type" content="concept" />
<meta name="DC.Title" content="Supported SSL and Transport Layer Security (TLS) protocols" />
<meta name="abstract" content="This topic describes which versions off the SSL and TLS protocols the i5/OS implementation supports." />
<meta name="description" content="This topic describes which versions off the SSL and TLS protocols the i5/OS implementation supports." />
<meta name="DC.Relation" scheme="URI" content="rzainconcepts.htm" />
<meta name="DC.Relation" scheme="URI" content="rzainhistory.htm" />
<meta name="DC.Relation" scheme="URI" content="http://www.rfc-editor.org/rfcsearch.html" />
<meta name="copyright" content="(C) Copyright IBM Corporation 2002, 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2002, 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="rzaintls" />
<meta name="DC.Language" content="en-us" />
<!-- All rights reserved. Licensed Materials Property of IBM -->
<!-- US Government Users Restricted Rights -->
<!-- Use, duplication or disclosure restricted by -->
<!-- GSA ADP Schedule Contract with IBM Corp. -->
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
<link rel="stylesheet" type="text/css" href="./ic.css" />
<title>Supported SSL and Transport Layer Security (TLS) protocols</title>
</head>
<body id="rzaintls"><a name="rzaintls"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Supported SSL and Transport Layer Security (TLS) protocols</h1>
<div><p>This topic describes which versions off the SSL and TLS protocols
the i5/OS™ implementation
supports.</p>
<div class="p">There are several versions of the SSL protocol defined. The latest version,
the Transport Layer Security Protocol (TLS), is based on SSL 3.0 and is a
product of the Internet Engineering Task Force (IETF). The i5/OS implementation
supports the following versions of the SSL and TLS protocols: <ul><li>TLS Version 1.0</li>
<li>TLS Version 1.0 with SSL Version 3.0 compatibility <div class="note"><span class="notetitle">Note:</span> <ol><li>Specifying TLS Version 1.0 with SSL Version 3.0 compatibility means that
TLS will be negotiated if possible and if that is not possible then SSL Version
3.0 will be negotiated. If SSL Version 3.0 cannot be negotiated, the SSL
handshake will fail.</li>
<li>The iSeries system also supports TLS Version 1.0 with SSL Version 3.0 and SSL Version 2.0
compatibility. This is specified with the protocol value of <strong>ALL</strong>,
which means that TLS will be negotiated if possible and if that is not possible
then SSL Version 3.0 will be negotiated. If SSL Version 3.0 cannot be negotiated,
SSL Version 2.0 will be negotiated. If SSL Version 2.0 cannot be negotiated,
the SSL handshake will fail.</li>
</ol>
</div>
</li>
<li>SSL Version 3.0</li>
<li>SSL Version 2.0</li>
<li>SSL Version 3.0 with SSL Version 2.0 compatibility</li>
</ul>
</div>
<div class="section"><h4 class="sectiontitle">SSL Version 3.0 versus SSL Version 2.0</h4><div class="p"> SSL version
3.0 is an almost totally different protocol compared to SSL Version 2.0.
Some of the major differences between the two protocols include: <ul><li>SSL Version 3.0 handshake protocol flows are different than SSL Version
2.0 handshake flows.</li>
<li>SSL Version 3.0 uses the BSAFE 3.0 implementation from RSA Data Security,
Incorporated. BSAFE 3.0 includes a number of timing attack fixes and the
SHA-1 hashing algorithm. The SHA-1 hashing algorithm is considered to be
more secure than the MD5 hashing algorithm. SHA-1 allows SSL Version 3.0
to support additional cipher suites which use SHA-1 instead of MD5. </li>
<li>SSL Version 3.0 protocol reduces man-in-the-middle (MITM) type of attacks
from occurring during SSL handshake processing. In SSL Version 2.0, it was
possible, though unlikely, that a MITM attack might accomplish cipher specification
weakening. Weakening the cipher can allow an unauthorized person to break
the SSL session key.</li>
</ul>
</div>
</div>
<div class="section"><h4 class="sectiontitle">TLS Version 1.0 versus SSL Version 3.0</h4><p>The latest
industry standard SSL protocol based on SSL version 3.0 is Transport Layer
Security (TLS) Version 1.0. Its specifications are defined by the Internet
Engineering Task Force (IETF) in RFC 2246, <cite>The TLS Protocol.</cite>.</p>
<div class="p"> The
major goal of TLS is to make SSL more secure and to make the specification
of the protocol more precise and complete. TLS provides these enhancements
over SSL Version 3.0: <ul><li>A more secure MAC algorithm</li>
<li>More granular alerts</li>
<li>Clearer definitions of "gray area" specifications</li>
</ul>
</div>
<p>Any iSeries™ server
applications that are enabled for SSL will automatically obtain TLS support
unless the application has specifically requested to use only SSL Version
3.0 or SSL Version 2.0. </p>
<div class="p">TLS provides the following security improvements: <ul><li><strong>Key-Hashing for Message Authentication</strong>TLS uses Key-Hashing for
Message Authentication Code (HMAC), which ensures that a record cannot be
altered while travelling over an open network such as the Internet. SSL Version
3.0 also provides keyed message authentication, but HMAC is more secure than
the (Message Authentication Code) MAC function that SSL Version 3.0 uses.
<p></p>
</li>
<li><strong>Enhanced Pseudorandom Function (PRF)</strong> PRF generates key data. In
TLS, the HMAC defines the PRF. The PRF uses two hash algorithms in a way which
guarantees its security. If either algorithm is exposed, the data will remain
secure as long as the second algorithm is not exposed. <p></p>
</li>
<li><strong>Improved finished message verification</strong>Both TLS Version 1.0 and
SSL Version 3.0 provide a finished message to both endpoints that authenticates
that the exchanged messages were not altered. However, TLS bases this finished
message on the PRF and HMAC values, which again is more secure than SSL Version
3.0. <p></p>
</li>
<li><strong>Consistent certificate handling</strong>Unlike SSL Version 3.0, TLS attempts
to specify the type of certificate which must be exchanged between TLS implementations. <p></p>
</li>
<li><strong>Specific alert messages</strong>TLS provides more specific and additional
alerts to indicate problems that either session endpoint detects. TLS also
documents when certain alerts should be sent. <p></p>
</li>
</ul>
</div>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzainconcepts.htm" title="SSL concepts includes supplemental information, providing some basic building blocks for the Secure Sockets Layer (SSL) protocols.">Concepts</a></div>
</div>
<div class="relconcepts"><strong>Related concepts</strong><br />
<div><a href="rzainhistory.htm" title="Netscape developed The Secure Sockets Layer Protocol (SSL) in 1994, as a response to the growing concern over security on the Internet.">History of SSL</a></div>
</div>
<div class="relinfo"><strong>Related information</strong><br />
<div><a href="http://www.rfc-editor.org/rfcsearch.html" target="_blank">The TLS Protocol</a></div>
</div>
</div>
</body>
</html>