Protected Extensible Authentication Protocol: Difference between revisions

Revision as of 14:18, 12 May 2014

Latest revision as of 16:36, 5 July 2024

(43 intermediate revisions by 37 users not shown)

Line 1:

{{Short description|Protocol that encapsulates Extensible Authentication Protocol}}

: ''PEAP is also an acronym for [[Personal Egress Air Packs]].''

<span lang="English" dir="ltr">The</span> '''Protected Extensible Authentication Protocol''', also known as '''Protected EAP''' or simply '''PEAP''', is a protocol that encapsulates the [[Extensible Authentication Protocol]] (EAP) within an encrypted and authenticated [[Transport Layer Security]] (TLS) [[tunneling protocol|tunnel]].<ref>{{cite news

| url=httphttps://www.zdnet.com/bloghome-and-office/ounetworking/understanding-the-updated-wpa-and-wpa2-standards/67

| title=Understanding the updated WPA and WPA2 standards

| work=ZDNet

| author=

| date=2005-06-02

| accessdateaccess-date=2012-07-17 }}

</ref><ref>Microsoft's PEAP version 0, [//tools.ietf.org/html/draft-kamath-pppext-peapv0-00 draft-kamath-pppext-peapv0-00], §1.1</ref><ref name="peapv2-10_abstract">Protected EAP Protocol (PEAP) Version 2, [//tools.ietf.org/html/draft-josefsson-pppext-eap-tls-eap-10 draft-josefsson-pppext-eap-tls-eap-10], abstract</ref><ref>Protected EAP Protocol (PEAP) Version 2, [//tools.ietf.org/html/draft-josefsson-pppext-eap-tls-eap-10 draft-josefsson-pppext-eap-tls-eap-10], §1</ref> The purpose was to correct deficiencies in EAP; EAP assumed a protected communication channel, such as that provided by physical security, so facilities for protection of the EAP conversation were not provided.<ref>Protected EAP Protocol (PEAP) Version 2, [//tools.ietf.org/html/draft-josefsson-pppext-eap-tls-eap-07 draft-josefsson-pppext-eap-tls-eap-07], §1</ref>

Line 21 ⟶ 22:

* PEAPv1/EAP-GTC

PEAPv0 and PEAPv1 both refer to the outer authentication method and are the mechanisms that create the secure TLS tunnel to protect subsequent authentication transactions. EAP-MSCHAPv2, and [[Extensible Authentication Protocol#EAP-GTC, and |EAP-SIMGTC]] refer to the inner authentication methods which provide user or device authentication. A third authentication method commonly used with PEAP is [[Extensible Authentication Protocol#EAP-SIM|EAP-SIM]].

Within Cisco products, PEAPv0 supports inner EAP methods EAP-MSCHAPv2 and EAP-SIM while PEAPv1 supports inner EAP methods EAP-GTC and EAP-SIM. Since Microsoft only supports PEAPv0 and doesn’tdoesn't support PEAPv1, Microsoft simply calls PEAPv0it "PEAP" without the v0 or v1 designator. Another difference between Microsoft and Cisco is that Microsoft only supports the EAP-MSCHAPv2 method and not the EAP-SIM method.

However, Microsoft supports another form of PEAPv0 (which Microsoft calls PEAP-EAP-TLS) that many Cisco and other third-party server and client software don’tdon't support. PEAP-EAP-TLS requires client installation of a [[client-side]] [[digital certificate]] or a more secure smartcard. PEAP-EAP-TLS is very similar in operation to the original EAP-TLS but provides slightly more protection because portions of the client certificate that are unencrypted in EAP-TLS are encrypted in PEAP-EAP-TLS. Ultimately, PEAPv0/EAP-MSCHAPv2 is by far the most prevalent implementation of PEAP, due to the integration of PEAPv0 into [[Microsoft Windows]] products. Cisco's CSSC client (discontinued in 2008 <ref>{{Cite web|title=End-of-Sale and End-of-Life Announcement for the Cisco Secure Services Client v4.0|url=https://www.cisco.com/c/en/us/products/collateral/wireless/secure-services-client/EOL_c51-459086.html|access-date=2021-05-04|website=Cisco|language=en}}</ref>) now supports PEAP-EAP-TLS.

PEAP has been so successful in the market place that even [[Funk Software]] (acquired by [[Juniper Networks]] in 2005), the inventor and backer of [[EAP-TTLS]], hadadded nosupport choice but to supportfor PEAP in their server and client software for wireless networks.

==PEAPv0 with EAP-MSCHAPv2==

MS-CHAPv2 is an old authentication protocol which Microsoft introduced with NT4.0 SP4 and Windows 98.

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]], meaning it allows authentication to databases that support the MS-CHAPv2 format, including Microsoft NT and Microsoft Active Directory.

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, and [[wpa supplicantwpa_supplicant]].

As with other 802.1X and EAP types, [[dynamic encryption]] can be used with PEAP.

A CA certificate must be used at each client to authenticate the server to each client before the client submits authentication credentials. If the CA certificate is not validated, in general it is trivial to introduce a fake Wireless Access Point which then allows gathering of [[MS-CHAPv2]] handshakes.<ref name="Man-in-the-Middle in Tunneled Authentication Protocols">{{cite web|title=Man-in-the-Middle in Tunneled Authentication Protocols|url=http://eprint.iacr.org/2002/163.pdf|publisher=Nokia Research Center|accessdate=14 November 2013}}</ref> On recent hardware those handshakes can be cracked quickly.

Several weaknesses have been found in MS-CHAPv2, some of which severely reduce the complexity of brute-force attacks making them feasible with modern hardware.<ref>{{Cite web |date=2016-03-16 |title=Divide and Conquer: Cracking MS-CHAPv2 with a 100% success rate |url=https://www.cloudcracker.com/blog/2012/07/29/cracking-ms-chap-v2/ |archive-url=https://web.archive.org/web/20160316174007/https://www.cloudcracker.com/blog/2012/07/29/cracking-ms-chap-v2/ |archive-date=2016-03-16 |access-date=2022-10-19 }}</ref>

== PEAPv1 with EAP-GTC ==

Line 46 ⟶ 51:

[[Nokia E66]] and later mobile phones ship with a version of [[Symbian]] which includes EAP-GTC support.

LDAP (Lightweight Directory Access Protocol) only supportsupports EAP-GTC.{{citation needed|date=March 2017}}

Android natively support EAP-GTC but IOS doesn't. <br/>

LDAP (Lightweight Directory Access Protocol) only support EAP-GTC.

==References==

Line 53 ⟶ 57:

==External links==

* {{cite IETF

* [http://www.watersprings.org/pub/id/draft-kamath-pppext-peapv0-00.txt draft-kamath-pppext-peapv0] - Microsoft's PEAP version 0

|title=Microsoft's PEAP version 0 (Implementation in Windows XP SP1)

|draft=draft-kamath-pppext-peapv0-00

|last1=Kamath |first1=Vivek |author1-link=

|last2=Palekar |first2=Ashwin |author2-link=

|last3=Wodrich |first3=Mark |author3-link=

|date=25 October 2002

|publisher=[[Internet Engineering Task Force|IETF]]

|accessdate=

}}

* [http://www.potaroo.net/ietf/idref/draft-josefsson-pppext-eap-tls-eap/ draft-josefsson-pppext-eap-tls-eap] - The EAP-TLS protocol specifications

<!--

* [http://articles.techrepublic.com.com/5100-1035-6148579.html Configure RADIUS for secure 802.1x wireless LAN]

* [http://articles.techrepublic.com.com/5100-1035-6148560.html How to self-sign a RADIUS server for secure PEAP or EAP-TTLS authentication]

-->

{{Authentication APIs}}

[[Category:Open standards]]

[[Category:Computer access control protocols]]

[[Category:Transport Layer Security]]