<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Not sure if it's the same thing as you asking for.<br>
But I've recently been bugging guus every so nicely for socks
support just for stuff like this.<br>
Check it out a recent git pull<br>
<br>
Using socks you can easily run tinc over other carriers, say like
Tor.<br>
Setup your super sekret node that nobody must know the location on
as a Tor hidden node and then you can let clients connect to the
sensitive node/nodes via Tor.<br>
Or course, Tor is only a single example. There is an entire pile of
various anonymising toys out there that become accessible via the
recently added socks support.<br>
<br>
The nature of the full automatic meshing which Tinc supports
however. You can't do that as is, without exposing end-point
identity... Otherwise you'd not be able to do the automatic direct
connections that are one of Tincs primary functions.<br>
<br>
It's a VPN. not an anonymizing transport... The 2 are rather
different beasts... However as I suggested above if you engage in a
little creative use of Tor over socks you can do VPN /over/
anonymizing Transport of your choice :3<br>
<br>
TunnelServer=yes and only peering individuals with the server as
guus suggested above would also work. <br>
<br>
<div class="moz-signature">Regards,<br>
<i>Nin lil'izi</i><br>
<br>
GPG Fingerprint: C510 909B 811E D6F5 0DFF 5D91 CF03 8FEA FD69 4622<br>
.<br>
..:<br>
</div>
<br>
On 07/05/12 10:50, Andrew Cowie wrote:
<blockquote
cite="mid:1336384229.6377.2.camel@turminder-xuss.roaming.operationaldynamics.com"
type="cite">
<pre wrap="">On Mon, 2012-05-07 at 10:58 +0200, Guus Sliepen wrote:
</pre>
<blockquote type="cite">
<pre wrap="">However, if not all your peers trust each other, my advice would be not to put
them all in the same VPN.
</pre>
</blockquote>
<pre wrap="">
Heh.
Although it does raise an interesting question. I can imagine a scenario
where participants have been allowed to join a VPN (say, in order to
punch through firewalls so they can thence communicate more "easily")
but are otherwise *not* mutually trusting. Indeed, in some cases, any
leakage of client end-point identity can be dangerous [to them!]. Be
interesting to know how best to handle that.
AfC
Sydney
_______________________________________________
tinc mailing list
<a class="moz-txt-link-abbreviated" href="mailto:tinc@tinc-vpn.org">tinc@tinc-vpn.org</a>
<a class="moz-txt-link-freetext" href="http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc">http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc</a>
</pre>
</blockquote>
</body>
</html>