Release: obfs4proxy-0.0.10
Hello, I just tagged obfs4proxy-0.0.10. The primary changes are a minor fix to the meek_lite behavior when using `utls` as the TLS implementation, and a series of updates (primarily following upstream) to the `utls` library. Tarball/Signature: https://people.torproject.org/~yawning/releases/obfs4proxy/obfs4proxy-0.0.10... https://people.torproject.org/~yawning/releases/obfs4proxy/obfs4proxy-0.0.10... Changes in version 0.0.10 - 2019-04-12: - Disable behavior distinctive to crypto/tls when using utls. - Bump the version of the utls fork. Regards, -- Yawning Angel
FYI, obfs4proxy no longer recognizes address:port in this form: ServerTransportListenAddr obfs4 [000.000.000.000]:443 Note the square brackets. Tor 0.3.5.8 / 0.4.0.5 still parses this syntax, and obfs4proxy used to too. As of 0.0.10 it no longer does. On 4/12/19 1:31 AM, Yawning Angel wrote:
On Sat, May 04, 2019 at 03:27:53PM +0000, Yawning Angel wrote:
Might be this? tor_addr_parse is overly permissive https://bugs.torproject.org/23082
Hi, On 5 May 2019, at 07:02, Steve Snyder <swsnyder@snydernet.net> wrote:
You're right: tor's internal lookup function has a similar bug, which we didn't fix in 23082. Tor uses separate functions for IP address parsing and hostname lookups, and they handle IPv4 addresses in square brackets differently. I opened a ticket for this issue, and submitted a fix which uses the same address parser on all IP addresses: https://trac.torproject.org/projects/tor/ticket/30721 We won't backport this fix, because it changes config parsing. So it will probably end up in tor 0.4.2.1-alpha and later. T
participants (5)
-
blacklight447＠tutanota.com -
David Fifield -
Steve Snyder -
teor -
Yawning Angel