[tor-bugs] #6411 [Tor]: Adding hidden services through control socket

Tor Bug Tracker & Wiki blackhole at torproject.org
Sun Mar 22 15:12:34 UTC 2015


#6411: Adding hidden services through control socket
-------------------------+-------------------------------------------------
     Reporter:           |      Owner:  yawning
  kevinevans             |     Status:  needs_review
         Type:           |  Milestone:  Tor: 0.2.7.x-final
  enhancement            |    Version:  Tor: 0.2.3.19-rc
     Priority:  normal   |   Keywords:  hidden-service control maybe-
    Component:  Tor      |  proposal tor-hs globalleaks-wants
   Resolution:           |  Parent ID:  #8993
Actual Points:           |
       Points:           |
-------------------------+-------------------------------------------------

Comment (by yawning):

 Replying to [comment:43 special]:
 > * The spec repeatedly uses 'Onion Services', but all other documentation
 still says 'Hidden services'. The reader may wonder what the difference is
 between these 'Onion Services' and the hidden services they can create via
 the configuration.

 Maybe.  I figured we had to start using the new and improved terminology
 somewhere.

 > * GET_ONIONS could be a GETINFO command instead, but I can't think of
 any particular benefit to changing it

 If this would be more consistent, this could easily be changed.  If people
 who do control port stuff think this should be folded into GETINFO, I'll
 change it.

 > * Because GET_ONIONS doesn't return services from other control
 connections, there is no way to comprehensively list services published by
 tor. They're not confidential either, though: those service names can (I
 think) appear in asynchronous events.

 This is somewhat future proof in that the reply format returns flags.  So
 this could easily be modified/extended in the future to return all the
 things.  The only reason this currently exists is so people hopefully
 manage "Detach"ed Onion Services correctly (though I'd prefer if people
 ignored the fact that it's possible to create those in the first place).

 Maybe the spec should mandate ignoring unknown flags in the GET_ONIONS
 response?

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


More information about the tor-bugs mailing list