[tor-bugs] #1859 [Tor Client]: Using 'mytorexitnode.exit' request when mytorexitnode is both exit and client

Tor Bug Tracker & Wiki torproject-admin at torproject.org
Tue Aug 24 03:33:48 UTC 2010


#1859: Using 'mytorexitnode.exit' request when mytorexitnode is both exit and
client
------------------------+---------------------------------------------------
 Reporter:  mwenge      |       Owner:                     
     Type:  defect      |      Status:  needs_review       
 Priority:  normal      |   Milestone:                     
Component:  Tor Client  |     Version:  Tor: 0.2.2.12-alpha
 Keywords:              |      Parent:                     
------------------------+---------------------------------------------------

Comment(by Sebastian):

 So, a bit of new info. We closed #641 because using .exit notation with
 your own exit *works* after you have seen your own descriptor in the
 consensus and added it to the routerlist. So this bug is only about the
 time between startup and becoming a part of the consensus for the first
 time.

 What we should do here is treat the request like it requested an unknown
 relay, and fail quickly.

 When I looked into the history, I noticed that for both
 router_get_by_nickname() and router_get_by_digest() we once had the
 ability to return our own routerinfo, independent of whether it had gotten
 into the consensus or not. This was introduced in 8efb2a957. In
 9c67ae34f106, however, the ability to return your own routerinfo was
 removed from router_get_by_digest().

 nickm and arma should look into which behaviour we actually want. Being
 inconsistent clearly causes problems here.

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


More information about the tor-bugs mailing list