Tor2web should automatically configure its own Tor instance as its Rendezvous Point

[fpietrosanti]

Tor2web, to reduce it's latency and increase it's peed, should automatically configure itself as it's rendezvous point as specified by the Tor Tickets:

https://trac.torproject.org/projects/tor/ticket/12844 https://trac.torproject.org/projects/tor/ticket/9685

To do that a Tor2web node should probably become an unpublished Tor Relay with ORPort open and the Tor2webRendezvousPoints become itself.

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[virgil]

In my case I have several modes that all use the same hardcoded RP. Having the nodes automatically configure to each use itself as the RP would make my life noticeably harder.

I prefer to keep it as an option that advanced users can set in their torrc.

I do like the idea of unpublished for relays being the RP though.

[fpietrosanti]

@virgil Isn't always better to have local Tor to be an "Unpublished Bridge" or "Unpublished Relay" (to let it open ORPort, it must be tested which is the right setup) and use localhost for performance reasons?

[virgil]

In my case, no. There are five backend t2w nodes, and for each transaction the node is selected randomly. Ideally the RP re-uses already established circuits. Ergo setting all of the nodes to use the same RP makes maximum re-use. In my case, having every node use the same RP (on the same local network) is better than having a separate RP for each t2w node's localhost.