Đang chuẩn bị liên kết để tải về tài liệu:
Scalable voip mobility intedration and deployment- P20

Scalable voip mobility intedration and deployment- P20: The term voice mobility can mean a number of different things to different people. Two words that can be quite trendy by themselves, but stuck together as if forgotten at a bus station long past the last ride of the night, the phrase rings a number of different, and at times discordant, bells. | 190 Chapter 5 The first step of MSCHAPv2 is for the server to request the identity of the client. The next step is for the client to respond in an encrypted form with the real identity of the user Table 5.33 . If the previous outer response had been something arbitrary the server will find out about the real username this way. Table 5.33 802.11 PEAP encrypted response identity Destination Address Source Address EAP Code TLS Type EAP Code encrypted EAP Type encrypted Identity encrypted Client Address AP Address Response Application Data Response Identity LOCATION user The server then responds with a challenge Table 5.34 . The challenge is a 16-byte random string which the client will use to prove its identity. Table 5.34 802.11 PEAP encrypted MSCHAPv2 challenge Destination Address Source Address EAP Code TLS Type EAP Code encrypted EAP Type encrypted CHAP Code encrypted Challenge encrypted Client Address AP Address Request Application Data Request MSCHAPv2 Challenge random The client responds to the challenge. First it provides a 16-byte random challenge of its own. This is used along with the server challenge the username and the password to provide an NT response Table 5.35 . Table 5.35 802.11 PEAP encrypted MSCHAPv2 response Destination Address Source Address EAP Code TLS Type EAP Code encrypted CHAP Code encrypted Peer Challenge encrypted Response encrypted AP Address Client Address Response Application Data Response Response random NT response Assuming the password matches the server will respond with an MSCHAPv2 Success message Table 5.36 . The success message includes some text messages which are intended to be user printable but really are not. The client now responds with a success message of its own Table 5.37 . The server sends out an EAP TLV message now still encrypted indicating success Table 5.38 . The exchange exists to allow extensions to PEAP to be exchanged in the encrypted www.newnespress.com Introduction to Wi-Fi 191 Table 5.36 802.11 PEAP .