From: Etienne Dechamps <etienne@edechamps.fr>
Date: Sun, 17 May 2015 18:23:12 +0000 (+0100)
Subject: Don't send KEY_CHANGED messages if we don't support the legacy protocol.
X-Git-Tag: release-1.1pre12~154^3
X-Git-Url: https://git.tinc-vpn.org/git/browse?a=commitdiff_plain;h=2cb216d83d825fcca2fa2b66c756b253f8f0828b;p=tinc

Don't send KEY_CHANGED messages if we don't support the legacy protocol.

KEY_CHANGED messages are only useful to invalidate keys for non-SPTPS nodes;
SPTPS nodes use a different internal mechanism (forced KEX) for that purpose.
Therefore, if we know we can't talk to legacy nodes, there's no point in
sending them these messages.
---

diff --git a/src/protocol_key.c b/src/protocol_key.c
index c183ac45..6721aa44 100644
--- a/src/protocol_key.c
+++ b/src/protocol_key.c
@@ -36,6 +36,7 @@
 static bool mykeyused = false;
 
 void send_key_changed(void) {
+#ifndef DISABLE_LEGACY
 	send_request(everyone, "%d %x %s", KEY_CHANGED, rand(), myself->name);
 
 	/* Immediately send new keys to directly connected nodes to keep UDP mappings alive */
@@ -43,6 +44,7 @@ void send_key_changed(void) {
 	for list_each(connection_t, c, connection_list)
 		if(c->edge && c->node && c->node->status.reachable && !c->node->status.sptps)
 			send_ans_key(c->node);
+#endif
 
 	/* Force key exchange for connections using SPTPS */