62 lines
4.3 KiB
HTML
62 lines
4.3 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="reference" />
|
|
<meta name="DC.Title" content="CHAP-MD5" />
|
|
<meta name="abstract" content="Challenge Handshake Authentication Protocol (CHAP-MD5) uses an algorithm (MD-5) to calculate a value that is known only to the authenticating system and the remote device." />
|
|
<meta name="description" content="Challenge Handshake Authentication Protocol (CHAP-MD5) uses an algorithm (MD-5) to calculate a value that is known only to the authenticating system and the remote device." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiysysauth.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiyclients.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiypap.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiyeap.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiypap.htm" />
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
|
|
<meta name="DC.Format" content="XHTML" />
|
|
<meta name="DC.Identifier" content="rzaiychap" />
|
|
<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>CHAP-MD5</title>
|
|
</head>
|
|
<body id="rzaiychap"><a name="rzaiychap"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">CHAP-MD5</h1>
|
|
<div><p><strong>Challenge Handshake Authentication Protocol (CHAP-MD5)</strong> uses
|
|
an algorithm (MD-5) to calculate a value that is known only to the authenticating
|
|
system and the remote device.</p>
|
|
<div class="section"><p>With CHAP, the user ID and the password are always encrypted,
|
|
so it is a more secure protocol than Password Authentication Protocol
|
|
(PAP). This protocol is effective against playback and trial-and-error access
|
|
attempts. CHAP authentication can occur more than once during a connection.</p>
|
|
</div>
|
|
<div class="section"><p>The authenticating system sends a challenge to the remote device
|
|
that is attempting to connect to the network. The remote device responds with
|
|
a value that is calculated by a common algorithm (MD-5) that both devices
|
|
use. The authenticating system checks the response against its own calculation.
|
|
Authentication is acknowledged when the values match; otherwise, the connection
|
|
is ended.</p>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaiysysauth.htm" title="PPP connections with an iSeries server support several options for authenticating both remote clients dialing in to the iSeries, and connections to an ISP or other server that the iSeries is dialing.">System authentication</a></div>
|
|
</div>
|
|
<div class="relref"><strong>Related reference</strong><br />
|
|
<div><a href="rzaiyclients.htm" title="Remote users, such as telecommuters or mobile clients, often require access to a company's network. These dial-in clients can gain access to an iSeries server with PPP.">Scenario: Connect remote dial-in clients to your iSeries server</a></div>
|
|
<div><a href="rzaiypap.htm" title="Password Authentication Protocol (PAP) uses a two-way handshake to provide the peer system with a simple method to establish its identity.">PAP</a></div>
|
|
<div><a href="rzaiyeap.htm" title="Extensible Authentication Protocol (EAP) allows third-party authentication modules to interact with the PPP implementation.">EAP</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |