Talk:Extensible Authentication Protocol

From Wikipedia, the free encyclopedia
Jump to: navigation, search
WikiProject Computing / Networking / Security (Rated C-class, Low-importance)
WikiProject icon This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
C-Class article C  This article has been rated as C-Class on the project's quality scale.
 Low  This article has been rated as Low-importance on the project's importance scale.
Taskforce icon
This article is supported by Networking task force (marked as Mid-importance).
Taskforce icon
This article is supported by WikiProject Computer Security (marked as Mid-importance).
 

Untitled[edit]

This page seems to have some serious anti-Cisco slant, possibly to the extent that it violates NPOV. In particular, phrases such as 'Swallowing the Cisco Kool-Aid' have no place in an encyclopdiac entry. Yes, it is true that LEAP as well as MD5 are vulernable to dictionary attacks; however, this article makes such the assinine references that EAP-FAST is likewise going to be insecure which is true speculation and also has no place in this entry. --anon

Thanks for pointing that out: I've cut a few sentences that were blatant, but it still needs work, and the article is pretty hard to understand to boot. I've added a "cleanup" tag. — Matt Crypto 16:29, 24 Jun 2005 (UTC)
I apologize for that 'Swallowing the Cisco Kool-Aid' comment. This was my first contribution to the Wiki and it was a newbie mistake. I will be more careful in the future. -- George

The EAP should, according to IETF (see http://www3.ietf.org/proceedings/02mar/slides/eap-1/tsld010.htm), be pronounced as "ee ey pee". Schotti 03:22, 16 February 2006 (UTC)

I made the small changes to the LEAP section and I would like to add I do not work for Cisco nor am I associated with them in any way other than as an end-user. I actually have a personal general bias against them due to their use of proprietary protocols everywhere (EIGRP anyone?). -Matt

Tagged Changed[edit]

This article seems pretty clean. I swapped out the cleanup for diagram because security protocols are inherently difficult to understand. --meatclerk 19:16, 23 July 2006 (UTC)

The data on the difference between PEAPv0 and PEAPv1 is wrong.

Both versions of PEAP support EAP subtypes and microsoft has an extension API allowing their use. Which supplicants support what by default or per supplicant implementation is not the same as saying they are not supported or various EAP subtypes that work in v0 can't work in v1 or vis versa. I've personally used EAP-GTC over PEAPv0 using the AEGIS supplicant.

The difference between v0 and v1 is that v0 uses a slightly different header format and v0 uses the eap type of EAP Extension (Type 33) to convey success/failure information. This is the ONLY difference between v0 and v1. From the users perspective neither version is better than the other. They both have the same capabilities and security properties and capabile of supporting the same subtypes.

The latest PEAP drafts define PEAPv2 which is similiar to v1 except that it adds a crypto binding between the inner EAP-PEAP-(EAP-??) method protected by PEAP and the keying material used in the PEAP handshake. This provides improved security.

RFC status[edit]

Why is RFC 2716 (EAP-TLS) called "open standard", whereas RFC 4746 (EAP-PSX) is called "experimental RFC"? Both are "experimental track" RFCs, but it sounds like someone is twisting words here. To the uninitiated, RFCs can be one of standards track: These have the IETF stamp of approval for future direction and relevancy. informational: Often non-normative documents, or contributed documents from vendors who wish to publish what they've implemented. experimental: A suggested protocol or similar which is, well, experimental. IETF will not publish bad or inconsistent protocols, so there is nothing derogatory about being an experimental RFC. BGP started out as experimental, and didn't become standards track until BGP-4! Finally, there's historic: obsolete standards.

It is also stated that EAP-MD5 is the only standards track EAP application, but this is not strictly correct -- the Diameter EAP application (RFC 4072) is also standards track. Kjetilho (talk) 11:58, 3 February 2008 (UTC)

EAP-MD5 _was_ the only standards track EAP method for quite some time. RFC 4072 is an EAP encapsulation for Diameter, not a method. However, since your comment the IETF EAP Methods Update (EMU) Working Group has passed EAP-GPSK (RFC 5433) and others are in progress. Davesnotthere (talk) 17:46, 28 February 2013 (UTC)

Merge proposal[edit]

I've added templates suggesting a merge of Protected Extensible Authentication Protocol into this article. The PEAP redirect should become a disambig page at that point, since there is a line at the top of the page about a different expansion of the acronym. Todd Vierling (talk) 15:42, 6 August 2008 (UTC)

  • I disagree. The material belongs in both, not one or the other. The tech is too complicated to fit neatly into a broader article with other highly complicated tech. By all means add whatever relevant material to the EAP article, but that section of the article should refer here for a complete understanding of the subject of PEAP. In other words, this article should redirect (on the subject of PEAP) to PEAP and not vice versa. Int21h (talk) 09:37, 20 March 2010 (UTC)
  • I disagree. Articles like EAP-SIM and EAP-AKA are merely informative of existent EAP variants. However they might grow up in a extensible explanation about the protocol. This feasible scenario fits better with EAP and its variant articles to referring each other. JrBenito - Mobile Software Engineer (talk) 22:22, 21 March 2011 (UTC)

From RADIUS[edit]

The following text does not have anything to do with RADIUS. I've moved it here in case it's needed in the EAP article.

Some EAP methods establish a secure tunnel between an authenticator and the home AAA server before the transmission of sensitive data, providing relief for most of those concerns. In these cases, there is sometimes an outer identity in clear text transmitted outside the EAP tunnel - visible to proxies so they can route packets - which doesn't have to reveal much about the user's true identity, and an inner identity that does, which is transmitted inside the secure EAP tunnel.{{Fact|date=April 2009}}  kgrr talk 08:19, 30 April 2009 (UTC)

"WPA Extended EAP" and "WPA2 Extended EAP"[edit]

How do those fit into this article? Are they different EAP methods altogether?

See: [1]

[2]

85.97.254.28 (talk) 08:57, 5 May 2012 (UTC)

Those are Wi-Fi Alliance labels for the fact they are now testing the listed EAP methods as part of their WFA Wi-Fi branding. Davesnotthere (talk) 17:30, 28 February 2013 (UTC)