16.05.2014 Views

Wireless Security.pdf - PDF Archive

Wireless Security.pdf - PDF Archive

Wireless Security.pdf - PDF Archive

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

412 Chapter 18<br />

channel scanning/probing time. This re-authentication delay becomes even more of a<br />

bottleneck for real time applications like voice. Although this is not exactly a security<br />

loophole, it is a “ drawback ” of using the security.<br />

18.4.4 What’s Wrong with 802.11 Authentication?<br />

Authentication mechanisms suggested by 802.11 suffer from many drawbacks. As we<br />

saw, 802.11 specifies two modes of authentication—OSA and SKA. OSA provides no<br />

authentication and is irrelevant here.<br />

SKA works on a challenge-response system as explained in Section 18.4.2. The AP<br />

expects that the challenge it sends to the STA be encrypted using an IV and the preshared<br />

key. As described in Section 18.2.1, there is no method specified in WEP for each STA to<br />

be assigned a unique key. Instead all STAs and the AP in a BSS are configured with the<br />

same key. This means that even when an AP authenticates a STA using the SKA mode,<br />

all it ensures is that the STA belongs to a group of STAs which know the preshared key.<br />

There is no way for the AP to reliably determine the exact identity of the STA that is<br />

trying to authenticate to the network and access it. 8<br />

To make matters worse, many 802.11 deployments share keys across APs. This increases<br />

the size of the group to which a STA can be traced. All STAs sharing a single preshared<br />

secret key also makes it very difficult to remove a STA from the allowed set of STAs,<br />

since this would involve changing (and redistributing) the shared secret key to all<br />

stations.<br />

There is another issue with 802.11 authentication: it is one-way. Even though it provides<br />

a mechanism for the AP to authenticate the STA, it has no provision for the STA to<br />

be able to authenticate the network. This means that a rogue AP may be able to hijack<br />

the STA by establishing a session with it. This is a very plausible scenario given the<br />

plummeting cost of APs. Since the STA can never find out that it is communicating with a<br />

rogue AP, the rogue AP has access to virtually everything that the STA sends to it.<br />

Finally, SKA is based on WEP, discussed in Section 18.5. It therefore suffers from all the<br />

drawbacks that WEP suffers from too. These drawbacks are discussed in Section 18.5.1.<br />

8<br />

MAC addresses can be used for this purpose but they are not cryptographically protected in that it<br />

is easy to spoof a MAC address.<br />

www.newnespress.com

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

Saved successfully!

Ooh no, something went wrong!