Challenge-Handshake Authentication Protocol: Difference between revisions

Revision as of 20:17, 13 April 2022

Latest revision as of 07:44, 28 May 2024

(8 intermediate revisions by 6 users not shown)

Line 1:

{{Short description|Authentication protocol to validate users}}
In [[computing]], the '''Challenge-Handshake Authentication Protocol''' ('''CHAP''') is an [[authentication protocol]] originally used by [[Point -to Point Protocol|Point to -Point Protocol]] (PPP)]] to validate users. CHAP is also carried in other authentication protocols such as [[RADIUS]] and [[Diameter (protocol)|Diameter]].

Almost all [[network operating system]]s support PPP with CHAP, as do most [[network access server]]s. CHAP is also used in [[PPPoE]], for authenticating DSL users.

As the [[Point to Point Protocol|Point to Point Protocol (PPP)]] sends data unencrypted and "in the clear", CHAP is vulnerable to any attacker who can observe the PPP session. An attacker can see the usersuser's name, CHAP challenge, CHAP response, and any other information associated with the PPP session. The attacker can then mount an offline [[Dictionarydictionary attack]] in order to obtain the original password. When used in PPP, CHAP also provides protection against [[replay attack]]s by the peer through the use of a challenge which is generated by the authenticator, which is typically a [[network access server]].

Where CHAP is used in other protocols, it may be sent in the clear, or it may be protected by a security layer such as [[TLS|Transport Layer Security]] (TLS)]]. For example, when CHAP is sent over [[RADIUS]] using [[User Datagram Protocol|User Datagram Protocol]] (UDP)]], any attacker who can see the RADIUS packets can mount an offline [[Dictionarydictionary attack]], as with PPP.

CHAP requires that both the client and server know the clear-text version of the password, although the password itself is never sent over the network. Thus when used in PPP, CHAP provides better security as compared to [[Password Authentication Protocol]] (PAP) which is vulnerable for both these reasons.

===Benefits of CHAP===

When the peer sends CHAP, the authentication server will receive it, and obtain the "known good" password from a database, and perform the CHAP calculations. If the resulting hashes match, then the user is deemed to be authenticated. If the hashes do not match, then the usersuser's authentication attempt is rejected.

Since the authentication server has to store the password in clear-text, it is impossible to useruse different [[Password#Form_of_stored_passwordsForm of stored passwords|formats for the stored password]]. If an attacker were to steal the entire database of passwords, all of those passwords would be visible "in the clear" in the database.

When the peer sends CHAP, the authentication server will receive it, and obtain the "known good" password from a database, and perform the CHAP calculations. If the resulting hashes match, then the user is deemed to be authenticated. If the hashes do not match, then the users authentication attempt is rejected.

Since the authentication server has to store the password in clear-text, it is impossible to user different [[Password#Form_of_stored_passwords|formats for the stored password]]. If an attacker were to steal the entire database of passwords, all of those passwords would be visible "in the clear" in the database.

As a result, while CHAP can be more secure than PAP when used over a PPP link, it prevents more secure storage "at rest" than with other methods such as [[Password authentication protocol|PAP]].

===Variants===

===Variants===

[[MS-CHAP]] is similar to CHAP but uses a different hash algorithm, and allows for each party to authenticate the other.

==Working cycle==

CHAP is an authentication scheme originally 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 [[handshakingHandshake (computing)|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|access-date=24 November 2012|year=2007|publisher=McGraw-Hill Education (India) Pvt Limited|isbn=978-0-07-063414-5|pages=352–}}</ref>

CHAP is an authentication scheme originally 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|access-date=24 November 2012|year=2007|publisher=McGraw-Hill Education (India) Pvt Limited|isbn=978-0-07-063414-5|pages=352–}}</ref>

# After the completion of the link establishment phase, the authenticator sends a "challenge" message to the peer.

Line 33 ⟶ 30:

==CHAP packets==

{| class="wikitable"

|-

!Description

!1 byte

Line 40 ⟶ 36:

!1 byte

!Variable

!Variable

!variable

|-

|Challenge

Line 46 ⟶ 42:

|ID

|Length

|Challenge Lengthlength

|Challenge value

|Name

Line 54 ⟶ 50:

|ID

|Length

|Response Lengthlength

|Response value

|Name

Line 83 ⟶ 79:

== See also ==

{{wikibooks | Network Plus Certification/Security/User Authentication }}

* [[List of authentication protocols]]

* [[Password Authentication Protocol]]

Line 93 ⟶ 88:

== External links ==

{{wikibooks | Network Plus Certification/Security/User Authentication }}

* {{IETF RFC|1994}} PPP Challenge Handshake Authentication Protocol (CHAP)

* {{IETF RFC|2865}} Remote Authentication Dial In User Service ([[RADIUS]]): ''uses [[Password authentication protocol|PAP]] or CHAP''