[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #6031 [Tor Hidden Services]: Distinguish when a Tor HS is "not found" vs "not reachable" (exists / does not exists)
#6031: Distinguish when a Tor HS is "not found" vs "not reachable" (exists / does
not exists)
---------------------------------+------------------------------------------
Reporter: naif | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: Tor Hidden Services | Version:
Keywords: | Parent:
Points: | Actualpoints:
---------------------------------+------------------------------------------
Comment(by hellais):
I wrote a patch for this, you can find it inside of the feature-6031
branch here:
https://gitweb.torproject.org/user/art/tor.git/shortlog/refs/heads/feature-6031
The behavior I ended up choosing was REP code 0x23 for HS_NOT_FOUND and
0x24 for HS_UNREACHABLE.
I have a few questions though:
Is it sufficient to have reached to the end of
rend_client_refetch_v2_renddesc() to determine that the HS does not exist?
For passing to rend_client_desc_trynow (that from what I understand, must
be called to close also the pending connections) the fact that I am
failing because the HS does not exist I replace the query with the string
"hostnotfound". This is kind of hackish and may create problems when
invoking rend_cmp_service_ids in rend_client_desc_trynow, what is the
better way to do this?
Is overall the strategy for determining if a HS exists or is unreachable
valid?
--
Ticket URL: <https://trac.torproject.org:443/projects/tor/ticket/6031#comment:7>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs