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

[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
> configurable per bridge, and just reuse the utls Client Hello ID names:
> 	utls=HelloChrome_Auto

Done.

https://gitlab.com/yawning/obfs4/commit/e4020b18f7aaafe9f4cb345630bfe18a5e44a8d2

As long as there's enough bridge line interoperability between
implementations, I'm not particularly bothered if other people actually
do use utls.HelloGolang or not, I'm choosing not to.

As a side note:
Implementing support for the missing DH groups in utls is likely trivial
(assuming you don't care that it's vartime, extremely bad for actual
TLS, fine for meek_lite) and would increase compatibility a good amount.

That said HelloChrome_Auto and HelloIOS_Auto both work fine against the
Azure bridge, so it might not be worth the effort.

Regards,

-- 
Yawning Angel

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20190121/ef56eec6/attachment.sig>