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.

Migrate HTTPS everywhere to WebExtensions. Should be easy. #7389

Closed

Description

@andreicristianpetcu

Hi. I'm just a user not an addon dev but I think I migrated HTTPS everywhere to WebExtensions. It is signed and you can download it from here.

This is how I did this. I installed this addon went to chrome web store and installed in inside Firefox.

I downloaded the xpi from Chrome web store with the Foxified extension, unzipped it and I ran this commands:

npm install -g web-ext
web-ext sign --api-key $API_KEY --api-secret $API_SECRET -s HTTPS_Everywhere

HTTPS_Everywhere is the folder with the unzipped xpi addon.

Why migrate to web extensions? They use async APIs so they are faster, only one codebase for both browsers.

Activity

  1. andreicristianpetcu commented on Oct 20, 2016

    @andreicristianpetcu
    Author
  2. gitarra commented on Oct 20, 2016

    @gitarra
    Contributor
  3. Hainish commented on Oct 21, 2016

    @Hainish
    Member

    HTTPS Everywhere is already migrated to WebExtensions, this is what the Chromium version of the extension runs. We maintain a codebase for this and will be moving to this for Firefox with the deprecation of XPCOM. https://github.com/EFForg/https-everywhere/tree/master/chromium

  4. andreicristianpetcu commented on Oct 22, 2016

    @andreicristianpetcu
    Author

    Why not publish the Chromium version in addons.mozilla.org instead of the XPCOM version? The XPCOM version uses a lot more resources than the WebExtension version on Firefox and it already works in Firefox. The deprecation of XPCOM might take a while.

  5. Hainish commented on Oct 24, 2016

    @Hainish
    Member

    @andreicristianpetcu The WebExtensions addon works well in Firefox stable for desktop, but currently certain UI elements are lacking in WebExtensions for Fennec. Also, there is no API for inspecting the certificate chain in WebExtensions, which is necessary for us to continue to support submissions to the Decentralized SSL Observatory. Lastly, Tor Browser is based on Firefox ESR, and some UI elements lack full support in ESR (which is at Firefox 45 currently).

  6. jwatt commented on Feb 5, 2017

    @jwatt
    Contributor

    Doesn't Mozilla Bug 1149250 - Ensure Web Extensions surface allowing manual http->https (secure update) redirects not blocked by CORS checks need to be fixed? Or does HTTPS Everywhere not require that functionality any more somehow?

    Also for anyone that's interested it looks like Mozilla Bug 1322748 - Web extensions: SSL (TLS) status API request is the bug that needs to be fixed to support submissions to the Decentralized SSL Observatory.

  7. heubergen commented on Apr 27, 2017

    @heubergen

    Any update on this? Should't be this issue open as the XPCOM version is still published on AMO?

  8. Hainish commented on May 4, 2017

    @Hainish
    Member

    No. HTTPS Everywhere has already been migrated to WebExtensions. We're unable to switch HTTPSE on Firefox over to WebExtensions until Tor Browser rebases to FF 52 ESR, as I already stated: #7389 (comment)

    This is already on the roadmap, there is no need to open an additional, Firefox-specific issue for this.

  9. z3ntu commented on Jun 19, 2017

    @z3ntu

    Tor Browser 7.0.1 is based on Firefox 52.2.0 😃

  10. Hainish commented on Jun 19, 2017

    @Hainish
    Member

    Currently the main blocker to WebExtensions deployment on Firefox is a secure signing mechanism for the self-hosted version. See #9958 (comment)

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions