-When connecting to nodes that use the legacy protocol used in tinc 1.0, be
-aware that any security issues in tinc 1.0 will apply to tinc 1.1 as well. On
-September 6th, 2018, Michael Yonly contacted us and provided proof-of-concept
-code that allowed a remote attacker to create an authenticated, one-way
-connection with a node using the legacy protocol, and also that there was a
-possibility for a man-in-the-middle to force UDP packets from a node to be sent
-in plaintext. The first issue was trivial to exploit on tinc versions prior to
-1.0.30, but the changes in 1.0.30 to mitigate the Sweet32 attack made this
-weakness much harder to exploit. These issues have been fixed in tinc 1.0.35
-and tinc 1.1pre17. The new protocol in the tinc 1.1 branch is not susceptible
-to these issues. However, be aware that SPTPS is only used between nodes
-running tinc 1.1pre\* or later, and in a VPN with nodes running different
-versions, the security might only be as good as that of the oldest version.
+See [QUICKSTART.md](QUICKSTART.md) for a quick guide to get tinc up and running.
+Read the [manual](https://www.tinc-vpn.org/documentation-1.1/) for more detailed
+information.