Re: [tor-bugs] #16269 [meek]: add-on compatibility check occurs repeatedly

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#16269: add-on compatibility check occurs repeatedly
------------------------+-----------------
     Reporter:  mcs     |      Owner:  dcf
         Type:  defect  |     Status:  new
     Priority:  normal  |  Milestone:
    Component:  meek    |    Version:
   Resolution:          |   Keywords:
Actual Points:          |  Parent ID:
       Points:          |
------------------------+-----------------

Comment (by dcf):

 Replying to [ticket:16269 mcs]:
 > One way to fix this is to add code to the meek HTTP helper extension
 that flushes the browser prefs. to disk before it enters the blocking
 event loop.  There may be a better solution, but this seems to solve the
 problem.

 Does attachment:0001-Bug-16269-add-on-compatibility-check-occurs-
 repeated.patch still work if `savePrefFile(null)` comes before, not after,
 `setBoolPref("network.proxy.socks_remote_dns", false)`? We actually don't
 want to save network.proxy.socks_remote_dns=false in prefs.js; it's meant
 to be a change in memory only.

 The reason we want network.proxy.socks_remote_dns=true in prefs.js, even
 though we always override that setting immediately, is to prevent DNS
 leaks in case something goes wrong and someone manages to run the meek
 headless browser, thinking it's a Tor Browser. See:
  * comment:5:ticket:16269
  * [https://gitweb.torproject.org/pluggable-
 transports/meek.git/commit/?id=32ca07ca008f5d09492f4d2782130bd54c52acf5
 32ca07ca00]

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/16269#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs