[tor-bugs] #9685 [Tor]: Improve Tor2web mode performance by having Tor2web client to be the RendezVous Point

[Tor Bug Tracker & Wiki]

#9685: Improve Tor2web mode performance by having Tor2web client to be the
RendezVous Point
-----------------------------+------------------------------
     Reporter:  naif         |      Owner:
         Type:  enhancement  |     Status:  reopened
     Priority:  normal       |  Milestone:  Tor: unspecified
    Component:  Tor          |    Version:
   Resolution:               |   Keywords:  tor-hs tor2web
Actual Points:               |  Parent ID:
       Points:               |
-----------------------------+------------------------------

Comment (by teor):

 This setup may already be available via the config option:
 `ORPort 9123 NoAdvertise`
 And perhaps also:
 `PublishServerDescriptor 0`

 This will open the listed ORPort on all interfaces, but won't add it to
 the consensus.

 Open issues:
 * I'm pretty sure clients and middle relays will accept a RP that isn't in
 the consensus, but we should test this. (If `RefuseUnknownExits` is set to
 1 in the consensus, most relays will refuse to exit using a relay that not
 in the consensus. We should check that this doesn't block RPs.)
 * I don't think there's currently any way to prevent arbitrary
 clients/relays connecting to the ORPort and relaying non-RP traffic
 through the host to the rest of the Tor network, apart from excluding it
 from the consensus, therefore making it hard to discover. We could add an
 option which leaves the ORPort open to terminate RP connections, but
 disables (most/other) relaying (like ClientOnly).

 Is there any other issues which I've missed?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9685#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online