Content deleted Content added
Citation bot (talk | contribs) Removed parameters. | You can use this bot yourself. Report bugs here. | Suggested by Neko-chan | Category:Internet protocols | via #UCB_Category 44/275 |
m Task 18 (cosmetic): eval 3 templates: del empty params (3×); hyphenate params (4×); |
||
Line 1:
In [[computing]], the '''Challenge-Handshake Authentication Protocol''' ('''CHAP''') [[authentication|authenticates]] a user or network host to an authenticating entity. That entity may be, for example, an [[Internet service provider]].
CHAP provides protection against [[replay attack]]s by the peer through the use of an incrementally changing identifier and of a variable challenge-value. CHAP requires that both the client and server know the plaintext of the secret, although it is never sent over the network. Thus, CHAP provides better security as compared to [[Password Authentication Protocol]] (PAP) which is vulnerable for both these reasons. The [[MS-CHAP]] variant does not require either peer to know the plaintext and does not transmit it, but has been broken.<ref>{{cite web|url=https://www.cloudcracker.com/blog/2012/07/29/cracking-ms-chap-v2/|title=Divide and Conquer: Cracking MS-CHAPv2 with a 100% success rate
==Working cycle==
CHAP is an authentication scheme used by [[Point-to-Point Protocol]] (PPP) servers to validate the identity of remote clients. CHAP periodically verifies the identity of the [[client (computing)|client]] by using a [[handshaking|three-way handshake]]. This happens at the time of establishing the initial [[Link Control Protocol|link (LCP)]], and may happen again at any time afterwards. The verification is based on a [[shared secret]] (such as the client's password).<ref name="Forouzan2007">{{cite book|author=Forouzan|title=Data Communications & Networking 4E Sie|url=https://books.google.com/books?id=6HaNKmfBK1oC&pg=PA352|
# After the completion of the link establishment phase, the authenticator sends a "challenge" message to the peer.
Line 60:
|publisher=[[Cisco Systems|Cisco tech note]]
|year=2005
|
== See also ==
|