16.05.2014 Views

Wireless Security.pdf - PDF Archive

Wireless Security.pdf - PDF Archive

Wireless Security.pdf - PDF Archive

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Wireless</strong> Embedded System <strong>Security</strong> 607<br />

MSCHAPv2<br />

EAP<br />

EAP-GTC<br />

TLS<br />

PEAPv0, EAP-TTLS<br />

PEAPv1<br />

EAP-TLS<br />

EAP-SIM<br />

EAP<br />

802.1X<br />

802.11b/g<br />

EAP was originally implemented for WPA2, and at the time the only EAP-variant required<br />

for Wi-Fi Alliance compliance (needed to use the trademarked Wi-Fi name and logo on a<br />

product) was called EAP-TLS, TLS being the Transport Layer <strong>Security</strong> protocol. However,<br />

the number of EAP variants has grown considerably, as various vendors have created their<br />

own mechanisms, all slightly different. Now, there are a total of 5 variants required to<br />

be compliant: EAP-TLS, EAP-TTLS/MSCHAPv2 8 (TTLS is simply “Tunnelled TLS ” ),<br />

PEAPv0/MSCHAPv2 (Protected EAP, which establishes a TLS connection over which<br />

EAP methods are used), PEAPv1/EAP-GTC (an EAP variant developed Cisco), and<br />

EAP-SIM which is essentially authentication using SIM cards for the telecom industry.<br />

In any case, Wi-Fi authentication is a dynamic and complex field and keeping up with it<br />

can be quite a challenge (by the time you are reading this it is likely that there have been<br />

a number of new protocols added and compliance requirements have changed). If you are<br />

interested in learning more about the wide array of authentication mechanisms for Wi-Fi,<br />

there are numerous online resources and there are even a few books on the subject. A good<br />

place to start is the Wi-Fi Alliance website itself: www.wi-fi.org . Figure 23.2 shows the<br />

relationships between the different authentication mechanisms used by Wi-Fi.<br />

23.1.5 Drowning in Acronyms<br />

Figure 23.2 : Wi-Fi authentication mechanisms<br />

The alphabet soup of Wi-Fi authentication protocols begs one important question: What<br />

do we need to support? Well, like we have talked about before, we need to adapt the<br />

protocol to our application. If you are implementing the latest and greatest consumer<br />

gadget and you must be compliant with every wireless access point under the sun, you<br />

8<br />

MSCHAP is a variant of the PPP CHAP protocol developed by Microsoft. MSCHAPv2 is<br />

described in RFC 2759.<br />

www.newnespress.com

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!