Protected Extensible Authentication Protocol: Difference between revisions

Content deleted Content added
No edit summary
No edit summary
Line 7:
PEAP is a joint proposal by [[Cisco Systems]], [[Microsoft]] and [[RSA Security]] as an open standard. It is already widely available in products, and provides very good security. It is similar in design to [[EAP-TTLS]], requiring only a server-side PKI certificate to create a secure TLS tunnel to protect user authentication.
 
As of May of 2005, there were two PEAP sub-types certified for the updated [[WPA]] and [[WPA2]] standard. They are:
* PEAPv0/EAP-MSCHAPv2
* PEAPv1/EAP-GTC
Line 14:
PEAPv0/EAP-MSCHAPv2 is the most common form of PEAP in use, and what is usually referred to as PEAP. The inner authentication protocol is [[Microsoft]]'s [[MS-CHAPv2|Challenge Handshake Authentication Protocol]].
 
Behind [[EAP-TLS]], PEAPv0/EAP-MSCHAPv2 is the second most widely supported EAP standard in the world. There are client and server implementations of it from various vendors, including support in all recent releases from [[Microsoft]], [[Apple Computer]] and [[Cisco Systems|Cisco]]. Other implementations exist such as the [[xsupplicant]] from the Open1x.org project.
 
== PEAPv1/EAP-GTC ==