[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #9815 [Obfsproxy]: Pluggable transports should learn Tor's data directory
#9815: Pluggable transports should learn Tor's data directory
-------------------------+-------------------------------------------------
Reporter: phw | Owner: asn
Type: | Status: needs_revision
enhancement | Milestone:
Priority: normal | Version:
Component: | Keywords: pluggable transport, state
Obfsproxy | location, persistent information
Resolution: | Parent ID:
Actual Points: |
Points: |
-------------------------+-------------------------------------------------
Comment (by phw):
Replying to [comment:4 asn]:
> following yesterday's discussion, and assuming that we will proceed with
the construction-based approach, would you be interested in writing that
`TransportConfig` (or whatever) class so that we can pass more options to
transports in a smooth way? We can then refactor my #8979 patch to use the
`TransportConfig` class too (it's currently using a method-based
approach).
Personally, I like the constructor-based approach as long as we have a
`TransportConfig`. I'll come up with a patch for it.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9815#comment:5>
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