>Number:         2446
>Category:       misc
>Synopsis:       The expansion of CHAP is incorect in the pppd man page
>Confidential:   yes
>Severity:       non-critical
>Priority:       low
>Responsible:    misc-bug-people (Misc Bug People)
>State:          open
>Class:          doc-bug
>Submitter-Id:   net
>Arrival-Date:   Mon May 20 12:05:06 1996
>Last-Modified:
>Originator:     John A. Maier
>Organization:
Datastorm Technologies
**********************************************************************
*       John A. Maier          * Research Assistant For Datastorm    *
* E-mail: johnam@datastorm.com * Technologies Inc. (Procomm Plus)    *
*                              * (314) 443-3283                      *
**********************************************************************
>Release:        1.1
>Environment:
	i386, NetBSD, i386, man/cat8/pppd.0
System: NetBSD jam.datastorm.com 1.1 NetBSD 1.1 (JAM) #25: Thu Mar 28 17:15:58 CST 1996 root@jam.datastorm.com:/usr/src/sys/arch/i386/compile/JAM i386


>Description:
>How-To-Repeat:
	man pppd
>Fix:
	In the pppd man page, change Cryptographic to Challenge.
>Audit-Trail:
>Unformatted:
>Descripion:
	In the RFCs, CHAP is expanded as...
	RFC 1334
	Challenge-Handshake Authentication Protocol

	In the pppd man page, CHAP is expanded as...
	+chap  Require  the peer to authenticate itself using CHAP
	       [Cryptographic Handshake  Authentication  Protocol]
	       authentication.

	Since the RFC is the difinitive source on issues like these,
	it would seen that our pppd man page is wrong.