58 lines
3.8 KiB
HTML
58 lines
3.8 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="PAP" />
|
||
|
<meta name="abstract" content="Password Authentication Protocol (PAP) uses a two-way handshake to provide the peer system with a simple method to establish its identity." />
|
||
|
<meta name="description" content="Password Authentication Protocol (PAP) uses a two-way handshake to provide the peer system with a simple method to establish its identity." />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzaiysysauth.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzaiychap.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzaiyeap.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzaiychap.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="rzaiypap" />
|
||
|
<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>PAP</title>
|
||
|
</head>
|
||
|
<body id="rzaiypap"><a name="rzaiypap"><!-- --></a>
|
||
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
<h1 class="topictitle1">PAP</h1>
|
||
|
<div><p><dfn class="term">Password Authentication Protocol (PAP)</dfn> uses
|
||
|
a two-way handshake to provide the peer system with a simple method to establish
|
||
|
its identity.</p>
|
||
|
<div class="section"><p>The handshake is conducted when establishing a link. After the
|
||
|
link is established, the remote device sends a user ID and password pair to
|
||
|
the authenticating system. Depending on the correctness of the pair, the authenticating
|
||
|
system either continues or ends the connection.</p>
|
||
|
</div>
|
||
|
<div class="section"><p>PAP authentication requires the user name and password to be sent
|
||
|
to the remote system in clear text form. With PAP, the user ID and password
|
||
|
are never encrypted which makes them possible to trace and vulnerable to hacker
|
||
|
attack. For this reason, you should use CHAP whenever possible.</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="rzaiychap.htm" title="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.">CHAP-MD5</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>
|