]> tinc-vpn.org Git - tinc/commit
projects / tinc / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 30e839b) | patch
Don't send KEY_CHANGED messages if we don't support the legacy protocol.
authorEtienne Dechamps <etienne@edechamps.fr>
Sun, 17 May 2015 18:23:12 +0000 (19:23 +0100)
committerEtienne Dechamps <etienne@edechamps.fr>
Sun, 17 May 2015 18:27:20 +0000 (19:27 +0100)
commit2cb216d83d825fcca2fa2b66c756b253f8f0828b
tree66fe875276f425fdd1482c96f604e6a02c8c6581tree | snapshot
parent30e839b0a1810b9cb0a2de2595cef2f8ebb06357commit | diff
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.
src/protocol_key.c diff | blob | history
tinc, the VPN daemon