+
+4. Detailed "example" of communication
+---------------------------------------
+
+Tinc uses a peer-to-peer protocol, but during the authentication phase we will
+make a distinction between a server (a tinc daemon listening for incoming
+connections) and a client (a tinc daemon that is trying to connect to the tinc
+daemon playing server).
+
+The message strings here are kept short for clarity. The real length of the
+exchanged messages is indicated. The capital words ID, CHALLENGE, CHAL_REPLY,
+META_KEY and ACK are in reality replaced by the numbers 0, 1, 2, 3 and 4
+respectively.
+
+daemon message
+--------------------------------------------------------------------------
+server <listening for connection>
+client <tries to connect>
+server <accepts connection>
+client ID client 8 0
+ | | +-> options
+ | +---> version
+ +-------> name of tinc daemon
+server CHALLENGE 57fb4b2ccd70d6bb35a64c142f47e61d
+ \______________________________/
+ +-> KEYLENGTH bits totally random string, encrypted
+ with client's public RSA key
+client CHAL_REPLY 191e23
+ +-> 160 bits SHA1 value of the complete decrypted
+ CHALLENGE sent by the server
+server ID server 8 0
+ | | +-> options
+ | +---> version
+ +-------> name of tinc daemon
+client CHALLENGE da02add1817c1920989ba6ae2a49cecb
+ \______________________________/
+ +-> KEYLENGTH bits totally random string, encrypted
+ with server's public RSA key
+server CHAL_REPLY 2bdeed
+ +-> 160 bits SHA1 value of the complete decrypted
+ CHALLENGE sent by the client
+client META_KEY 5f0823a93e35b69e7086ec7866ce582b
+ \______________________________/
+ +-> KEYLENGTH bits totally random string, encrypted
+ with server's public RSA key
+server META_KEY 6ab9c1640388f8f045d1a07f8a672630
+ \______________________________/
+ +-> KEYLENGTH bits totally random string, encrypted
+ with client's public RSA key
+client ACK
+server ACK
+--------------------------------------------------------------------------
+
+When the server receives the ACK from the client, it should prepare itself
+for the fact that any subsequent data will be encrypted with the key the server
+sent itself in the META_KEY. Ofcourse, this key is taken from the decrypted
+version of that META_KEY, so that we will know for sure only the real client
+can send us messages. The same goes for the client when it receives an ACK.
+
+5. Encryption of VPN packets
+-----------------------------
+
+The VPN packets are also encrypted, but with a different key than the one used
+for the meta connection. The reason is that VPN packets can also come from
+other clients which do not have a meta connection with server. Each tinc daemon
+propagates (on request) a separate key for packets that it receives. This key
+is a random string, generated on the fly. Since it is exchanged using the meta
+connection, this key itself will be encrypted.