Hi,
On 5 May 2019, at 07:02, Steve Snyder wrote:
> On 5/4/19 12:26 PM, David Fifield wrote:
>> On Sat, May 04, 2019 at 03:27:53PM +, Yawning Angel wrote:
>>> On 5/3/19 1:48 PM, Steve Snyder wrote:
FYI, obfs4proxy no longer recognizes address:port in this form:
On 5/4/19 12:26 PM, David Fifield wrote:
> On Sat, May 04, 2019 at 03:27:53PM +, Yawning Angel wrote:
>> On 5/3/19 1:48 PM, Steve Snyder wrote:
>>> FYI, obfs4proxy no longer recognizes address:port in this form:
>>>
>>> ServerTransportListenAddr obfs4 [000.000.000.000]:443
>>>
>>> Note
On Sat, May 04, 2019 at 03:27:53PM +, Yawning Angel wrote:
> On 5/3/19 1:48 PM, Steve Snyder wrote:
> > 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
On 5/3/19 1:48 PM, Steve Snyder wrote:
> 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
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
What a great news, thanks for your work!
Apr 12, 2019, 7:31 AM by yawn...@schwanenlied.me:
> 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
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:
