Next: A real life example Up: Computer network security Previous: OLSR and security Contents
Schemes to secure OLSR routing traffic have been proposed in both [17] and [33]. The solution proposed in [17] requires state to be kept for every received packet or signature and uses a rather complex time synchronization scheme. [33] proposes a solution using a single signature for entire OLSR packets, but the signature itself is not carried in an OLSR message, thus breaking RFC3626 compatibility. The latter solution does not prevent replay attacks since no timestamps/sequence-numbers are used.
As this thesis does not focus on security, no deeper analysis of related work, or security as a term, will be done.