[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 atagar):
> From what I can understand, this isn't possible with the microdescriptor
exit policy because it only contains a list of ports.
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?
We probably need to answer this question before we can figure out a decent
object model. Sebastian might be a good person to ask since I vaguely
recall that he was involved with the introduction of microdescriptor exit
policies.
Note that this doesn't block us from making a class for *descriptor* exit
policies. Making that and tests would be a fine first step (and be
something that we could finally tie into the Descriptor class).
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/5454#comment:14>
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