]> git.meshlink.io Git - meshlink/commit
Be liberal in accepting KEY_CHANGED/REQ_KEY/ANS_KEY requests.
authorGuus Sliepen <guus@tinc-vpn.org>
Sat, 23 Jan 2010 17:48:01 +0000 (18:48 +0100)
committerGuus Sliepen <guus@tinc-vpn.org>
Sat, 23 Jan 2010 17:48:01 +0000 (18:48 +0100)
commitd15099e0029578bfd24d6b464b941f4693280001
treef2e3880fe0fc12f210bfcb47ea13eb4436fd1df5
parent469fa318bc817908af9a51e3a980ffc998fae6f2
Be liberal in accepting KEY_CHANGED/REQ_KEY/ANS_KEY requests.

When we got a key request for or from a node we don't know, we disconnected the
node that forwarded us that request.  However, especially in TunnelServer mode,
disconnecting does not help. We now ignore such requests, but since there is no
way of telling the original sender that the request was dropped, we now retry
sending REQ_KEY requests when we don't get an ANS_KEY back.
src/graph.c
src/net_packet.c
src/node.h
src/protocol_key.c