Changes between Initial Version and Version 1 of Ticket #29077, comment 12


Ignore:
Timestamp:
Jan 26, 2019, 1:41:59 AM (5 months ago)
Author:
dcf
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #29077, comment 12

    initial v1  
    1 Here is a new candidate: meek branch [https://gitweb.torproject.org/pluggable-transports/meek.git/log/?h=utls_2&id=6c2cad6ce0e1d0d23ec88edb7942362de2552b0e utls_2]
     1Here is a new candidate:
     2 * meek branch [https://gitweb.torproject.org/pluggable-transports/meek.git/log/?h=utls_2&id=6c2cad6ce0e1d0d23ec88edb7942362de2552b0e utls_2]
     3 * tor-browser-build branch [https://gitweb.torproject.org/user/dcf/tor-browser-build.git/log/?h=meek-client-utls&id=1ad16caea0de2ba2445036a517247f2dd712ed13 meek-client-utls]
    24
    35This is a rewrite using the obfs4proxy-inspired technique (comment:4), with a few implementation differences. Instead of `dialTLS` being attached to the `RoundTripper` wrapper with a distinguised error code, use a standalone `dialUTLS` function. Store the state for the dynamically created `Transport` in a closure rather than in the parent struct. Raise an error if the ALPN changes.
     
    1719||`utls=HelloChrome_70` ||[https://tlsfingerprint.io/id/bc4c7e42f4961cd7 bc4c7e42f4961cd7] [https://web.archive.org/web/20190125222100/https://tlsfingerprint.io/id/bc4c7e42f4961cd7 archive] ||  3.54%||
    1820||`utls=HelloFirefox_63` ||[https://tlsfingerprint.io/id/6bfedc5d5c740d58 6bfedc5d5c740d58] [https://web.archive.org/web/20190125222153/https://tlsfingerprint.io/id/6bfedc5d5c740d58 archive] ||  1.66%||
     21
     22Browsing and Moat, using meek-azure, seem to be working fine.