[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #11156 [Tor]: "can't find a pluggable transport proxy" errors when obfsproxy started up
#11156: "can't find a pluggable transport proxy" errors when obfsproxy started up
-------------------------+-------------------------------------------------
Reporter: asn | Owner:
Type: defect | Status: needs_review
Priority: normal | Milestone: Tor: 0.2.5.x-final
Component: Tor | Version:
Resolution: | Keywords: 024-backport, tor-pt, tor-client,
Actual Points: | tbb-needs, nickm-review-0254
Points: | Parent ID:
-------------------------+-------------------------------------------------
Comment (by asn):
Replying to [comment:32 nickm]:
> Hm. The actual change is only a two-line change in
1a3eb5c72dd0feb43a542ca465c57dd0801ff7cc. The other stuff is just comments
and flag names. That's good.
>
Yes, the actual changes are not very many.
> The part I'm trying to figure out is, I'm comparing this patch to the
part of run_scheduled_events() where we do:
> {{{
> if (!net_is_disabled() && pt_proxies_configuration_pending())
> pt_configure_remaining_proxies();
> }}}
>
> Should this patch also check !net_is_disabled() in config.c?
Hm, I think it should. Thanks for catching that. I will write a new patch
tomorrow.
As I understand it, the `!net_is_disabled()` is there so that PT proxies
don't start up their listeners as long as `DisableNetwork` is enabled.
This needs to happen in `config.c` too, since calling
`pt_configure_remaining_proxies()` for the first time will set the
managed-proxy environent variables and launch the PT proxy, which will
then start up its listeners.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/11156#comment:33>
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