[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #5454 [Stem]: ExitPolicy Class for stem

#5454: ExitPolicy Class for stem
-------------------------+--------------------------------------------------
 Reporter:  gsathya      |          Owner:  atagar           
     Type:  enhancement  |         Status:  needs_information
 Priority:  normal       |      Milestone:                   
Component:  Stem         |        Version:                   
 Keywords:               |         Parent:                   
   Points:               |   Actualpoints:                   
-------------------------+--------------------------------------------------

Comment(by karsten):

 Replying to [comment:14 atagar]:
 > That seems weird. What is the use of the microdescriptor exit policy
 then? The point of an exit polity is to let the client know if you're
 willing to service a particular destination or not. If it doesn't answer
 that question, then how is it used by a tor client?

 Nick could answer this better, but AIUI, the purpose of an exit policy
 summary is to help the client make good path selection decisions without
 bloating directories.  With any summary, there may be false positives
 (connections that the relay doesn't support but which the summary implied
 would work) and false negatives (connections that the relay would support
 but which aren't contained in the summary).  The client will learn if the
 chosen relay supports the connection it attempts to make after building
 the circuit.  The idea is to stop wasting large amounts of client
 bandwidth on downloading descriptors, and exit policies can waste a lot of
 space there.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/5454#comment:18>
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