#11156: "can't find a pluggable transport proxy" errors when obfsproxy started
up
-------------------------+-------------------------------------------------
Reporter: asn | Owner:
Type: defect | Status: needs_revision
Priority: normal | Milestone: Tor: 0.2.5.x-final
Component: Tor | Version:
Resolution: | Keywords: 024-backport tor-pt tor-client,
Actual Points: | tbb-needs
Points: | Parent ID:
-------------------------+-------------------------------------------------
Comment (by nickm):
I'm not sure why the right fix here should involve changes to the
directory fetch logic at all. Wouldn't it be better to make it so that
instead of having PTs go into a "maybe reset this; I'll figure it out
later" state, we identify the ones that don't need to be reset
immediately, and leave them alone? Would that be super-hard?
I'm also not clear why we're using got_hup to indicate something that
isn't "received a HUP" but is instead "the configuration changed at some
point"
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/11156#comment:25>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
[email protected]
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
