[tor-bugs] #29430 [Applications/Tor Browser]: Use uTLS for meek TLS camouflage in Tor Browser

[Tor Bug Tracker & Wiki]

#29430: Use uTLS for meek TLS camouflage in Tor Browser
-------------------------------------------------+-------------------------
 Reporter:  dcf                                  |          Owner:  tbb-
                                                 |  team
     Type:  enhancement                          |         Status:
                                                 |  needs_revision
 Priority:  Medium                               |      Milestone:
Component:  Applications/Tor Browser             |        Version:
 Severity:  Normal                               |     Resolution:
 Keywords:  meek, utls, ff68-esr, tbb-9.0-must-  |  Actual Points:
  nightly, TorBrowserTeam201908                  |
Parent ID:                                       |         Points:
 Reviewer:                                       |        Sponsor:
                                                 |  Sponsor44-can
-------------------------------------------------+-------------------------
Changes (by gk):

 * keywords:  meek, utls, ff68-esr, tbb-9.0-must-nightly,
     TorBrowserTeam201908R => meek, utls, ff68-esr, tbb-9.0-must-nightly,
     TorBrowserTeam201908
 * status:  needs_review => needs_revision


Comment:

 Replying to [comment:26 mcs]:
 > Here is a patch for review:
 > https://gitweb.torproject.org/user/brade/tor-browser-
 build.git/commit/?h=bug29430-01&id=03c164be46b4bd2779e9816d24209b3f40ad668e

 We should make sure the updated code works for alpha as well. I think the
 {{{
 [% IF c("var/nightly") -%]
 }}}
 blocks need to get amended so that alphas are using the same code path
 (there is a corresponding `var/alpha` available) as well.

 > It does not address comment:24.

 If you look at the `mingw-w64` project you get a sense of how you can
 handle it. The config file has something like:
 {{{
   - filename: libtool-sort.patch
   - filename: 27503.patch
 }}}
 and then the build script are picking those up on top of the actual source
 code used by using `patch`:
 {{{
 patch -p1 -d gcc-[% c("var/gcc_version") %] < $rootdir/libtool-sort.patch
 }}}
 and
 {{{
 patch -p1 -d /var/tmp/build/[% project %]-[% c("version") %] <
 $rootdir/27503.patch
 }}}
 I think a similar approach would work here until we have a proper tag.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/29430#comment:28>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online