Skip to content
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
This repository was archived by the owner on Nov 6, 2023. It is now read-only.

Try implementing HTTPS Everywhere using WebExtensions #2640

Closed

Description

@jsha

According to this Mozilla blog post, Firefox is moving to a new WebExtensions model, which is supposed to be compatible with Chrome extensions: https://blog.mozilla.org/addons/2015/08/21/the-future-of-developing-firefox-add-ons/.

We have a long lead time before XPCOM is deprecated, and there are some big issues to solve, like how to make SSL Observatory work in such a world (probably we need Mozilla to implement some extra APIs).

We should try implementing HTTPS Everywhere using the new API, to see if it is possible. Probably starting from the Chromium code rather than the existing Firefox code makes the most sense.

Activity

  1. Mikaela commented on Sep 12, 2015

    @Mikaela
    Contributor

    I was wondering whether SSL Observatory is coming to Chrome or disappearing from Firefox too at #1681 (comment) and I was linked here after asking at OFTC and this issue answers my question.

    We have a long lead time before XPCOM is deprecated, and there are some big issues to solve, like how to make SSL Observatory work in such a world (probably we need Mozilla to implement some extra APIs).

    Would Proposal: native.js to “embrace & extend” the WebExtensions API help if Mozilla implements it?

  2. semenko commented on Jan 22, 2016

    @semenko
    Contributor

    So I took a cursory look here, and it'll be surprisingly easy to adapt the Chrome code to support the new WebExtensions model, and move to one unified extension codebase.

    There's great documentation here: https://developer.mozilla.org/en-US/Add-ons/WebExtensions

    And some issues to look at here: https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Chrome_incompatibilities

    As of now, it looks like:

    • SSL Observatory support may die: It's never going to work in Chrome, and it may stop working in Firefox without a new Mozilla API (see above comment)
    • We'll need to change some handlers to be platform specific and listen in onBeforeSendHeaders in Firefox -- Chrome lets us rewrite requests earlier (see https://developer.mozilla.org/en-US/Add-ons/WebExtensions/API/webRequest)
    • It's not clear we can catch redirect loops in Firefox
  3. DerekTurtleRoe commented on Feb 21, 2016

    @DerekTurtleRoe

    @semenko Can you explain why in detail that we won't be able to have the SSL Observatory? I saw and read the links, but I don't understand what you're referring to.

  4. semenko commented on Feb 21, 2016

    @semenko
    Contributor

    No APIs exist, that I'm aware of, that allow for access to TLS data in Chrome (or in the WebExtension model in Firefox).

    The Chrome dev team also announced that they won't be adding any new APIs to support accessing TLS info. (You can probably find a bug somewhere at https://crbug.com)

  5. DerekTurtleRoe commented on Feb 21, 2016

    @DerekTurtleRoe

    @semenko Well, that sucks. I wonder what purpose they have of not allowing TLS? Wouldn't it just make it more secure? Chrome isn't exactly the most secure or private browser, so you would think they would want to improve it when they can...

  6. Hainish commented on Oct 11, 2016

    @Hainish
    Member

    I'm closing this for now, we can reopen a separate issue for building the SSL Observatory into the WebExtensions codebase if the APIs become available at some point.

  7. Hainish commented on Oct 11, 2016

    @Hainish
    Member

    Thanks for all your work on this @semenko !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions