X-Git-Url: https://www.tinc-vpn.org/git/browse?p=tinc;a=blobdiff_plain;f=doc%2Ftinc.texi;h=6bbc2e24ef20c2b3af9ec1cc9399d4c7b5dc87b3;hp=0943f8484bc9cdefc3ecc9413b34644d0b17c25a;hb=67766d65f06854ee894d784f638c5c9cd2b50bca;hpb=c228da54d47657811dfb679e7f138cbba58a9f67 diff --git a/doc/tinc.texi b/doc/tinc.texi index 0943f848..6bbc2e24 100644 --- a/doc/tinc.texi +++ b/doc/tinc.texi @@ -15,7 +15,7 @@ This is the info manual for @value{PACKAGE} version @value{VERSION}, a Virtual Private Network daemon. -Copyright @copyright{} 1998-2010 Ivo Timmermans, +Copyright @copyright{} 1998-2011 Ivo Timmermans, Guus Sliepen and Wessel Dankers . @@ -39,7 +39,7 @@ permission notice identical to this one. @vskip 0pt plus 1filll This is the info manual for @value{PACKAGE} version @value{VERSION}, a Virtual Private Network daemon. -Copyright @copyright{} 1998-2010 Ivo Timmermans, +Copyright @copyright{} 1998-2011 Ivo Timmermans, Guus Sliepen and Wessel Dankers . @@ -119,7 +119,7 @@ computers on the other end of the Internet. This problem can be solved by using @emph{virtual} networks. Virtual networks can live on top of other networks, but they use encapsulation to keep using their private address space so they do not interfere with -the Internet. Mostly, virtual networks appear like a singe LAN, even though +the Internet. Mostly, virtual networks appear like a single LAN, even though they can span the entire world. But virtual networks can't be secured by using firewalls, because the traffic that flows through it has to go through the Internet, where other people can look at it.