Content deleted Content added
No edit summary |
m Dating maintenance tags: {{Dead link}} |
||
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 is specified in {{IETF RFC|1994}}.
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>{{dead link|date=April 2017}}{{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
| |||