[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #11393 [Pluggable transport]: Make an HTTP requestor Chrome extension for meek-client

#11393: Make an HTTP requestor Chrome extension for meek-client
-------------------------------------+----------------------
     Reporter:  dcf                  |      Owner:  clan
         Type:  project              |     Status:  assigned
     Priority:  normal               |  Milestone:
    Component:  Pluggable transport  |    Version:
   Resolution:                       |   Keywords:  meek
Actual Points:                       |  Parent ID:
       Points:                       |
-------------------------------------+----------------------
Changes (by dcf):

 * owner:  asn => clan
 * status:  new => assigned


Comment:

 Chang started doing this at https://github.com/changlan/meek/tree/chrome
 (and copied to https://gitweb.torproject.org/pluggable-
 transports/meek.git/shortlog/refs/heads/chrome). It is broken into two
 parts: and app and an extension, because extensions aren't allowed to open
 listening sockets in Chrome. It goes like this:
   meek-client â(socket)â app â(message)â extension â(HTTPS)â
 www.google.com
 According to https://developer.chrome.com/extensions/webRequest, it's not
 supposed to be possible to modify the Host header. But apparently it
 works. https://code.google.com/p/chromium/issues/detail?id=158073 is the
 bug report noting the discrepancy.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/11393#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