Re: [tor-dev] RFC: Using `utls` in meek_lite.

2019-01-23 Thread David Fifield
On Thu, Jan 24, 2019 at 07:44:48AM +, Yawning Angel wrote: > On 1/24/19 7:38 AM, David Fifield wrote: > > I see, you're right. It has to do with the reuse of the initConn. > > A proper "general" solution that solves that problem and the ALPN issue > is to have a `initConn` and

Re: [tor-dev] RFC: Using `utls` in meek_lite.

2019-01-23 Thread Yawning Angel
On 1/24/19 7:38 AM, David Fifield wrote: > I see, you're right. It has to do with the reuse of the initConn. A proper "general" solution that solves that problem and the ALPN issue is to have a `initConn` and `http.RoundTripper` instance per destination host, and some additional locking. With

Re: [tor-dev] RFC: Using `utls` in meek_lite.

2019-01-23 Thread David Fifield
On Thu, Jan 24, 2019 at 07:33:39AM +, Yawning Angel wrote: > On 1/24/19 6:47 AM, David Fifield wrote: > > // This also assumes that req.URL.Host will remain constant for the > > // lifetime of the roundTripper, which is a valid assumption for > > meeklite. > > > > Am I wrong, or is

Re: [tor-dev] RFC: Using `utls` in meek_lite.

2019-01-23 Thread Yawning Angel
On 1/24/19 6:47 AM, David Fifield wrote: > // This also assumes that req.URL.Host will remain constant for the > // lifetime of the roundTripper, which is a valid assumption for > meeklite. > > Am I wrong, or is the actual restriction less strict? You can reuse the > roundTripper for

Re: [tor-dev] RFC: Using `utls` in meek_lite.

2019-01-23 Thread David Fifield
On Mon, Jan 21, 2019 at 05:12:41AM +, Yawning Angel wrote: > I just pushed a change to obfs4proxy master to use `utls` to mask the > ClientHello signature (currently Chrome 70.x). > > https://gitlab.com/yawning/obfs4/commit/4d453dab2120082b00bf6e63ab4aaeeda6b8d8a3 // This also

Re: [tor-dev] RFC: Using `utls` in meek_lite.

2019-01-21 Thread Yawning Angel
(Whoops I sent my last reply directly instead of to the list. It wasn't all that important for the general public, and lists.tp.o has been flaky for me recently anyway.) On 1/21/19 5:22 PM, David Fifield wrote: > As for the TODO, my plan was was to expose a "utls" SOCKS arg to make it >

Re: [tor-dev] RFC: Using `utls` in meek_lite.

2019-01-21 Thread David Fifield
On Mon, Jan 21, 2019 at 05:12:41AM +, Yawning Angel wrote: > I just pushed a change to obfs4proxy master to use `utls` to mask the > ClientHello signature (currently Chrome 70.x). > > https://gitlab.com/yawning/obfs4/commit/4d453dab2120082b00bf6e63ab4aaeeda6b8d8a3 > > I understand that this

[tor-dev] RFC: Using `utls` in meek_lite.

2019-01-21 Thread Yawning Angel
Hello, I just pushed a change to obfs4proxy master to use `utls` to mask the ClientHello signature (currently Chrome 70.x). https://gitlab.com/yawning/obfs4/commit/4d453dab2120082b00bf6e63ab4aaeeda6b8d8a3 I understand that this is being worked on for the original meek (see: