[tor-bugs] #12844 [Tor]: Allow Tor2Web mode to specify its own Rendezvous Point

[Tor Bug Tracker & Wiki]

#12844: Allow Tor2Web mode to specify its own Rendezvous Point
------------------------+----------------------------------
     Reporter:  asn     |      Owner:
         Type:  task    |     Status:  closed
     Priority:  normal  |  Milestone:  Tor: 0.2.6.x-final
    Component:  Tor     |    Version:
   Resolution:  fixed   |   Keywords:  tor-hs, nickm-review
Actual Points:          |  Parent ID:
       Points:          |
------------------------+----------------------------------

Comment (by asn):

 Replying to [comment:36 virgilgriffith]:
 > @asn: I attempted this on some EC2 machines.  Can you paste me a log of
 one your tor2web instances correctly setting the RP to:
 >
 > "25199EBF02D6F9C93DEEC0CC15DC6F690ED928CA~OnionCityRP"
 >
 > I got the relay setup but so far no dice in getting the client tor2web
 machine to use it.
 >
 > If it helps the version of Tor I'm running on both the tor2web-node and
 the RP is "version 0.2.6.7 (git-c1a17aafcc854762)".

 The feature still seems to work for me, even with tor-0.2.6.7.
 Unfortunately, the OnionCityRP relay does not seem to be up.

 For my testing, I used the 'beer' relay and I set:
   `Tor2webRendezvousPoints B120B6310D626FA54B6667DCAFEBD17A1EF47890`
 in my torrc:
 https://globe.torproject.org/#/relay/B120B6310D626FA54B6667DCAFEBD17A1EF47890

 Then in my info logs I got:
 {{{
 Apr 20 23:33:58.000 [info] choose_good_exit_server(): Picked new RP:
 $B120B6310D626FA54B6667DCAFEBD17A1EF47890~beer at 193.166.167.68
 }}}

 FWIW, I will be less active the next weeks.

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