13.07.2015 Views

Page 2 Lecture Notes in Computer Science 2865 Edited by G. Goos ...

Page 2 Lecture Notes in Computer Science 2865 Edited by G. Goos ...

Page 2 Lecture Notes in Computer Science 2865 Edited by G. Goos ...

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.

Prevent<strong>in</strong>g Replay Attacks for Secure Rout<strong>in</strong>g <strong>in</strong> Ad Hoc Networks 145is not focused on one route any more [15][17]. But still some precious resourcesare wasted <strong>in</strong> the permitted range. If these attacks are performed frequently, theloss can be remarkable.In [11](Awerbuch et. al.), a confirmation for each data packet is required fromthe receiv<strong>in</strong>g node. By limit<strong>in</strong>g the number of missed data packets, the routewith poor quality will result <strong>in</strong> an <strong>in</strong>vestigation. It can detect the existence ofwormhole only after the degradation has been detected and it still needs tof<strong>in</strong>d another route to go over from the beg<strong>in</strong>n<strong>in</strong>g. Our proposal can preventwormholes from be<strong>in</strong>g formed.4 Our Proposal4.1 OverviewIt is important to note that the authentication of neighbors <strong>in</strong> AODV is weak.The neighbor<strong>in</strong>g mechanism <strong>in</strong> AODV is that each node adds a new neighborto its neighbor list whenever it hears a “reliable enough” signal no matter whosends the signal. A malicious node can send this signal <strong>by</strong> simply record<strong>in</strong>gpackets, spoof<strong>in</strong>g the MAC address (or not, if there is no MAC address mapp<strong>in</strong>gmechanism set up) to impersonate other nodes.The weak neighbor authentication gives room to perform the above two replayattacks. The basic idea of our solution is to measure the Round Trip Time(RTT) between two nodes to decide if they are true neighbors. For the RREQFlood<strong>in</strong>g attack (Fig.1), when B receives an RREQ, if it could check that thispacket could not be orig<strong>in</strong>ated from direct neighbor nodes <strong>by</strong> look<strong>in</strong>g at thevalue of RTT to the node, it would discard the request.For the wormhole attack (Fig.2), the situation is more complicated. Thewormhole attack has three scenarios if proper authentication mechanism hasbeen used to discrim<strong>in</strong>ate between outsiders and <strong>in</strong>siders; thus outsiders cannotparticipate <strong>in</strong> the operation of the network because they do not have legitimateidentifications: (1) M1 and M2 are both outsiders; (2) M1 is a collud<strong>in</strong>g <strong>in</strong>siderand M2 is an outsider or vice versa; (3) M1 and M2 are both <strong>in</strong>siders. In scenario(1), s<strong>in</strong>ce M1 and M2 are all transparent nodes the RREQ received <strong>by</strong> Z canonly come from A. In scenario (2), if M1 is an outsider and M2 selects not tohide (of course it will not hide because <strong>in</strong> that way Z would receive RREQ fromA and would know the existence of wormhole from RTT), it is also possiblefor Z to receive RREQ forwarded <strong>by</strong> M2 or <strong>by</strong> M1 <strong>in</strong> the second case. If theyexchange keys, then the case will be the same as <strong>in</strong> follow<strong>in</strong>g scenario. In scenario(3), Z may receive from A, M1 or M2. If M1 and M2 are all outsiders(1) then<strong>by</strong> measur<strong>in</strong>g RTT to A, node Z would know the existence of a wormhole. Forscenario (2)(3), node Z would receive RTT replies from any node as long as theyappear valid. Except those approaches detect<strong>in</strong>g wormhole after QoS(Quality ofService) degrades, current approaches cannot detect this type of attack yet.The proposal <strong>in</strong>volves send<strong>in</strong>g a verification message to un-trusted neighborsfor which a node receives RREQ for the first time. An un-trusted neighboris a neighbor that is not assured to be with<strong>in</strong> transmission range. From the

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

Saved successfully!

Ooh no, something went wrong!