Changes between Version 45 and Version 46 of doc/meek


Ignore:
Timestamp:
Apr 12, 2014, 5:22:13 AM (6 years ago)
Author:
dcf
Comment:

Explain that the list of HTTPS options is the summary of a discussion, and that we decided to go with a browser extension.

Legend:

Unmodified
Added
Removed
Modified
  • doc/meek

    v45 v46  
    199199=== How to look like browser HTTPS ===
    200200
    201 Some alternatives:
     201We decided to use a browser extension to make all the HTTPS requests required by meek, so that the requests look just like those made by a browser. There's an extension [ticket:11183 for Firefox] (which works with Tor Browser, so it can work in the browser bundle without shipping a second browser) and one [ticket:11393 for Chrome]. The list below is a summary of a discussion that took place [https://lists.torproject.org/pipermail/tor-dev/2014-February/006266.html on the tor-dev mailing list] and on IRC.
     202
    202203 1. Use your own HTTPS/TLS library, and take care to make sure your ciphersuites and extensions match those of a browser. There are [https://www.mozilla.org/projects/security/pki/python-nss/ Python bindings for NSS] that might make it easier. Chromium is [https://code.google.com/p/chromium/issues/detail?id=62803 moving to OpenSSL] in the future.
    203204 2. Use a separate (headless) browser as an instrument for making HTTPS requests. This is what [https://raw.github.com/wiki/gsathya/htpt/Overall_architecture2.png htpt plans to do].\\