[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_review
Priority: normal | Milestone: Tor: 0.2.3.x-final
Component: Tor Bridge | Version:
Keywords: | Parent:
Points: | Actualpoints:
------------------------+---------------------------------------------------
Comment(by asn):
In #5143, murble reports that IPv6 ORPort addresses are not passed
correctly to obfsproxy. He says that tor configured with `ORPort
"[::]:9001"`, passes `TOR_PT_ORPORT="127.0.0.1:0"` to obfsproxy.
The current `bug4865` branch passes `TOR_PT_ORPORT=":::9001"` to
obfsproxy, when tor is configured with `ORPort "[::]:9001"`. Maybe it
should be passing `TOR_PT_ORPORT="[::]:9001"`?
This doesn't look too hard to pull off. We will probably have to use a
variant of fmt_addr() that uses `tor_addr_to_str()` with `decorate` set to
`1`.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/4865#comment:9>
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