[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #4865 [Tor Bridge]: managed obfsproxy cannot talk to tor on other than 127.0.0.1
#4865: managed obfsproxy cannot talk to tor on other than 127.0.0.1
------------------------+---------------------------------------------------
Reporter: wwaites | Owner: asn
Type: defect | Status: needs_revision
Priority: normal | Milestone: Tor: 0.2.3.x-final
Component: Tor Bridge | Version:
Keywords: | Parent:
Points: | Actualpoints:
------------------------+---------------------------------------------------
Comment(by asn):
Should we make a `router_get_first_advertised_or_addr()`, which does a
`connection_get_by_type(CONN_TYPE_OR_LISTENER);` and returns its `addr`?
This way we should get the address of a lucky OR listener.
Or should we make a `get_primary_or_addr()` which acts like
`get_primary_or_port()`, looping through all the configured `port_cfg_t`s,
but returns the address instead of the port? I'm not sure how `port_cfg_t`
is created, and I'm not sure if that would simply return the configuration
file string.
Maybe we should also spec. this change, and mention that if a bridge has
multiple OR listeners, there is no rule to select a specific one to put in
`TOR_PT_ORPORT`. Or maybe we should make a rule?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/4865#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