<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://encyclopediaofcybersecurity.com/index.php?action=history&amp;feed=atom&amp;title=Challenge_Handshake_Authentication_Protocol</id>
	<title>Challenge Handshake Authentication Protocol - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://encyclopediaofcybersecurity.com/index.php?action=history&amp;feed=atom&amp;title=Challenge_Handshake_Authentication_Protocol"/>
	<link rel="alternate" type="text/html" href="https://encyclopediaofcybersecurity.com/index.php?title=Challenge_Handshake_Authentication_Protocol&amp;action=history"/>
	<updated>2026-05-06T13:40:35Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.41.1</generator>
	<entry>
		<id>https://encyclopediaofcybersecurity.com/index.php?title=Challenge_Handshake_Authentication_Protocol&amp;diff=336&amp;oldid=prev</id>
		<title>Ccocrick: Created page with &quot;== Challenge Handshake Authentication Protocol (CHAP) ==  The &#039;&#039;&#039;Challenge Handshake Authentication Protocol&#039;&#039;&#039; (CHAP) is an authentication protocol used to verify the identity of a user or client device attempting to connect to a network. CHAP is a secure method that prevents transmission of plaintext passwords over the network. It is commonly used with Point-to-Point Protocol (PPP) connections.  === Operation ===  When a user or client device initiates a connection to...&quot;</title>
		<link rel="alternate" type="text/html" href="https://encyclopediaofcybersecurity.com/index.php?title=Challenge_Handshake_Authentication_Protocol&amp;diff=336&amp;oldid=prev"/>
		<updated>2024-05-09T01:55:10Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;== Challenge Handshake Authentication Protocol (CHAP) ==  The &amp;#039;&amp;#039;&amp;#039;Challenge Handshake Authentication Protocol&amp;#039;&amp;#039;&amp;#039; (CHAP) is an authentication protocol used to verify the identity of a user or client device attempting to connect to a network. CHAP is a secure method that prevents transmission of plaintext passwords over the network. It is commonly used with Point-to-Point Protocol (PPP) connections.  === Operation ===  When a user or client device initiates a connection to...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;== Challenge Handshake Authentication Protocol (CHAP) ==&lt;br /&gt;
&lt;br /&gt;
The &amp;#039;&amp;#039;&amp;#039;Challenge Handshake Authentication Protocol&amp;#039;&amp;#039;&amp;#039; (CHAP) is an authentication protocol used to verify the identity of a user or client device attempting to connect to a network. CHAP is a secure method that prevents transmission of plaintext passwords over the network. It is commonly used with Point-to-Point Protocol (PPP) connections.&lt;br /&gt;
&lt;br /&gt;
=== Operation ===&lt;br /&gt;
&lt;br /&gt;
When a user or client device initiates a connection to a network using PPP, the network access server (NAS) challenges the client to prove its identity. The NAS sends a random string, known as a challenge, to the client. The client combines the challenge with its password using a cryptographic hash function, such as MD5, and sends the result back to the NAS. The NAS independently performs the same calculation using its copy of the client&amp;#039;s password. If the calculated values match, authentication is successful.&lt;br /&gt;
&lt;br /&gt;
=== Security ===&lt;br /&gt;
&lt;br /&gt;
CHAP provides stronger security compared to plaintext authentication protocols like Password Authentication Protocol (PAP) because it does not transmit passwords over the network. Instead, it uses a cryptographic hash function to verify passwords without exposing them to eavesdropping or password sniffing attacks.&lt;br /&gt;
&lt;br /&gt;
=== Advantages ===&lt;br /&gt;
&lt;br /&gt;
* CHAP provides stronger security compared to plaintext authentication protocols like PAP.&lt;br /&gt;
* It prevents transmission of passwords over the network, reducing the risk of unauthorized access.&lt;br /&gt;
&lt;br /&gt;
=== Disadvantages ===&lt;br /&gt;
&lt;br /&gt;
* CHAP requires both the client and server to store plaintext copies of the password or an equivalent reversible representation, which poses a security risk if these credentials are compromised.&lt;br /&gt;
* It requires more computational resources compared to plaintext authentication protocols.&lt;br /&gt;
&lt;br /&gt;
=== Alternatives ===&lt;br /&gt;
&lt;br /&gt;
Alternative authentication protocols include Password Authentication Protocol (PAP), which transmits passwords in plaintext, and Extensible Authentication Protocol (EAP), which supports a variety of authentication methods, including more secure mechanisms like Transport Layer Security (TLS) and digital certificates.&lt;br /&gt;
&lt;br /&gt;
== See Also ==&lt;br /&gt;
* [[Point-to-Point_Protocol|Point-to-Point Protocol (PPP)]]&lt;br /&gt;
* [[Password_Authentication_Protocol|Password Authentication Protocol (PAP)]]&lt;br /&gt;
* [[Extensible_Authentication_Protocol|Extensible Authentication Protocol (EAP)]]&lt;br /&gt;
* [[MD5|Message Digest Algorithm 5 (MD5)]]&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
* [https://tools.ietf.org/html/rfc1994 RFC 1994 - PPP Challenge Handshake Authentication Protocol (CHAP)]&lt;br /&gt;
&lt;br /&gt;
[[Category:Protocols]]&lt;/div&gt;</summary>
		<author><name>Ccocrick</name></author>
	</entry>
</feed>