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.

Known issue: Release 2020.3.16 breaks whitelisting of some URLS and "open insecure page" button for them. #19029

Closed

Description

@ivan-kolmychek

Type: code issue

Update to Release 2020.3.16 with new feature that allows manually whitelisting hosts seems to break whitelisting for few URLs that I'm using.

For example, if I have EASE enabled when I visit URL like http://abcd.local:4000 (which points to something along the lines of 127.x.y.z in my hosts file), I see the HTTPS Everywhere noticed you were navigating to a non-HTTPS page, even though I had whitelisted it in previous versions by pressing "open insecure page". Looking at the list of hosts I see an entry for abcd.local:4000 in there but it doesn't seem to be doing anything. Deleting it doesn't change anything, re-adding it also seems to have no effect.

Neither pressing "open insecure page" nor pressing "open insecure page for this session only" nor manually whitelisting it seems to work, so it seems that the only currently available workaround is to disable EASE.

Activity

  1. changed the title [-]Release 2020.3.16 breaks whitelisting of some pages and "open insecure page" for them.[/-] [+]Release 2020.3.16 breaks whitelisting of some URLS and "open insecure page" button for them.[/+] on Mar 17, 2020
  2. ivan-kolmychek commented on Mar 17, 2020

    @ivan-kolmychek
    Author

    Forgot to mention that it all is happening in Chromium 80.0.3987.132.

  3. cschanaj commented on Mar 17, 2020

    @cschanaj
    Collaborator

    #18760 introduced a regression for the whitelisting features, I have just filed a fix #19032.

  4. jmgurney commented on Mar 18, 2020

    @jmgurney

    And there appears to be no plans to do a release for a couple weeks:
    #19032 (comment)

  5. pipboy96 commented on Mar 18, 2020

    @pipboy96
    Contributor

    @jmgurney You may thank COVID-19 for that.

  6. jmgurney commented on Mar 18, 2020

    @jmgurney

    Thanks to @zoracon for providing a work around for this issue:
    #19032 (comment)

    Installing the previous 2019.11.7 fixes this issue for me. I do not know if auto updates will work in the future, or if this work around will have to regularly reapplied due to auto updates.

  7. added a commit that references this issue on Mar 18, 2020
    16c65b2
  8. jmgurney commented on Mar 18, 2020

    @jmgurney

    Another option is to turn off EASE (Encrypt All Sites Eligible), but if you have that turned on, likely you do for a very valid reason, and disabling that is likely worse than downgrading.

    #19032 (comment)

    P.S. @zoracon I'd recommend leaving this issue open until a release is pushed so that people can find these solutions instead of creating new issues. It was very easy to find when it was open since it was recent and near the top, but now that it's closed, it will be harder for people to find the solutions.

  9. pinned this issue on Mar 18, 2020
  10. ivan-kolmychek commented on Mar 23, 2020

    @ivan-kolmychek
    Author

    Thank you for reacting fast, fixing the issue and providing a workaround.

    Given the circumstances I think its totally understandable that release cannot be cut right now.

  11. zoracon commented on Mar 23, 2020

    @zoracon
    Contributor

    Thank you for reacting fast, fixing the issue and providing a workaround.

    @ivan-kolmychek Thank you for reporting concisely. The shelter-in-place order was rolled out while this release was being made. I really appreciate the understanding.

  12. pipboy96 commented on Mar 23, 2020

    @pipboy96
    Contributor

    Due to the fact this discussion is not realistically able to make the shelter-in-place order go away, I am locking this issue. @zoracon please reverse if appropriate.

  13. locked as resolved and limited conversation to collaborators on Mar 23, 2020
  14. changed the title [-]Release 2020.3.16 breaks whitelisting of some URLS and "open insecure page" button for them.[/-] [+]Known issue: Release 2020.3.16 breaks whitelisting of some URLS and "open insecure page" button for them.[/+] on Mar 30, 2020
  15. zoracon commented on May 21, 2020

    @zoracon
    Contributor

    Resolved with #19288

  16. unpinned this issue on May 21, 2020
  17. added a commit that references this issue on Jun 2, 2020
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

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions