[tor-bugs] #6031 [Tor Hidden Services]: Distinguish when a Tor HS is "not found" vs "not reachable" (exists / does not exists)

[Tor Bug Tracker & Wiki]

#6031: Distinguish when a Tor HS is "not found" vs "not reachable" (exists / does
not exists)
---------------------------------+------------------------------------------
 Reporter:  naif                 |          Owner:                    
     Type:  enhancement          |         Status:  needs_revision    
 Priority:  normal               |      Milestone:  Tor: 0.2.4.x-final
Component:  Tor Hidden Services  |        Version:                    
 Keywords:                       |         Parent:                    
   Points:                       |   Actualpoints:                    
---------------------------------+------------------------------------------

Comment(by naif):

 mmm but "connection refused" should be already used today when:
 - lookup is ok
 - introduction/redenzvous is ok
 - circuit is established
 - TCP port redirected on the Tor Hidden Service port-redirection is closed
 (and receive a "connection refused" from TCP-level-meaning of that).

 If we use "connection refused" we would not be able to detect the
 condition previously defined.

 The real matter is that socks does not let us to handle "dns resolution
 error" that is the stuff we are trying simulate.

 So i think that for that reason we would still need to use one of the
 unassigned/reserved socks error codes, and eventually update various
 libraries / internet draft stuff, to include a generic "host not found"
 that could apply to both TorHS and to normal hostname.

 What do you think?

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