[tahoe-dev] switching from introducers to gossip?

[erpo41 at gmail.com]

Could Bob choose his own node as the rendezvous point, totally eliminating
the load on the tor network?

On Wed, Jul 11, 2012 at 6:45 AM, Michael Rogers <michael at briarproject.org>wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 11/07/12 14:02, James A. Donald wrote:
> >> It seems people are only aware of the last feature because of
> >> the poorly chosen name.  IMO, the "hidden" aspect is one of the
> >> less interesting features.  I've heard a rumor that there's a
> >> proposal to make a version of this feature which provides the
> >> other features without the hidden part for the benefit of lower
> >> latency.
> >
> > This would be extremely convenient, for unhidden tor services could
> > not only provide lower latency, but could handle high bandwidth.
>
> I think it might be possible to handle this from the client side by
> building circuits with fewer than three hops.
>
> If I remember right, hidden services work something like this:
>
> * Alice, a client running a hidden service, chooses several
> introduction points and builds a circuit to each one
> * Alice anonymously publishes the addresses of the introduction points
> * Bob, a client wishing to contact Alice's hidden service, anonymously
> retrieves the addresses of the introduction points
> * Bob chooses a rendezvous point and builds a circuit to it
> * Bob builds a circuit to one of Alice's introduction points and
> informs Alice of the rendezvous point
> * If Alice accepts the connection, she builds a circuit to Bob's
> rendezvous point, which connects Alice's circuit to Bob's circuit
> * Alice and Bob communicate through the connected circuits
>
> Usually each circuit has three hops, but if Alice and Bob don't need
> to be anonymous or unlinkable they can use one-hop circuits. The final
> connection would have two hops: Alice <-> rendezvous point <-> Bob.
>
> The client is responsible for choosing the length of the circuit in
> Tor, so it should be possible to do this through a client library like
> Silvertunnel without modifying the protocol or the relays.
>
> Cheers,
> Michael
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
>
> iQEcBAEBAgAGBQJP/YNxAAoJEBEET9GfxSfMIWMH/RabIuZ362zznSbpvkzx5CBW
> ZWH3yxEVY9IbgeeY6dV/IP65ZVfrQa4caPXohbG8HbJj7XJp/ijnan15Z0TtkN2j
> 0ze9TSTZoU0Nk9KWfARBZ1Qdq3e7/Ui+RWNipjl+wjZtq4FVsmJ95hdqrUjKaNwK
> 3LKVTaXAIbjcgWFWCZ+Tqm/7NxN4SlssG2ewNvnd77TKzMMoRO9wOc5jaBxfxdFY
> q3co0mFndh4l3lRw23m/MNJC/MWbyKysG5OhkjVRmQ/cI4klSKBiF2dJwOS3flNC
> +5y8ry1vzo/ltG2Tkpa2fZE1a+uu9OuH9/PPCRcGJH15krTtZKNoVq/60EltaEA=
> =oKrm
> -----END PGP SIGNATURE-----
> _______________________________________________
> tahoe-dev mailing list
> tahoe-dev at tahoe-lafs.org
> https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20120711/755732bc/attachment.html>