[tor-bugs] #29347 [Obfuscation/meek]: Rewrite meek-http-helper as a WebExtension

[Tor Bug Tracker & Wiki]

#29347: Rewrite meek-http-helper as a WebExtension
------------------------------+------------------------------
 Reporter:  dcf               |          Owner:  dcf
     Type:  enhancement       |         Status:  needs_review
 Priority:  Medium            |      Milestone:
Component:  Obfuscation/meek  |        Version:
 Severity:  Normal            |     Resolution:
 Keywords:  webextension      |  Actual Points:
Parent ID:                    |         Points:
 Reviewer:                    |        Sponsor:
------------------------------+------------------------------

Comment (by gk):

 Replying to [comment:15 dcf]:
 > Replying to [comment:14 gk]:
 > > Replying to [comment:13 dcf]:
 > > > I worked on integrating the WebExtension into Tor Browser. It's
 working now and ready to be looked at.
 > > >  * [https://gitweb.torproject.org/pluggable-
 transports/meek.git/log/?h=webextension&id=de03366fbe1f23cbb21d41aec8f4913f189ecb8b
 meek]
 > > >  * [https://gitweb.torproject.org/user/dcf/tor-browser-
 build.git/commit/?h=meek-
 webextension&id=45192a1adcb29e6200f2b9e46d97bbdbbfb0a509 tor-browser-
 build]
 > > > I tested it on linux-x86_64 and windows-x86_64, but I'm not set up
 to test on osx.
 > >
 > > If we go with `meek_lite` in 9.0 as planned in #29430 and given that
 the currently available extension is working in Tor Browser, then it seems
 to me there is no need to review your changes from a Tor Browser
 perspective AND you don't need to worry about the macOS testing, right?
 >
 > That's correct, **but** there are two reasons why it's still worth
 having a meek browser extension:
 > 1. to mitigate the risk caused by switching to uTLS--it is a fallback in
 case something goes catastrophically wrong and can't be fixed quickly
 > 2. a browser extension building on meek will be the easiest way to
 prototype a transport based on ESNI

 Yes, those are good points. However, I'd like to understand what you think
 we should do for Tor Browser here. In particular, I was wondering whether
 to spend time on reviewing and testing your changes in a Tor Browser
 context *now*, with the aim to have all of that merged to the alpha series
 (so it will eventually be in stable at some point), given the current plan
 outlined in #29430.

 I mean testing a transport based on ESNI in an alpha (which needs an
 extension) should not be a problem once that is ready and we could easily
 review the extension and tor-browser-build integration then.

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