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.

Flickr logins don't work (Firefox only?) #728

Closed

Description

@BillWeiss

In Firefox, running HTTPS Everywhere 4.0.2 with the default ruleset, attempting to log in to Flickr leads to a page with the below text (at https://www.flickr.com/register_cookies.gne, titled "no cookied") after logging in. Disabling the Flickr rule (but keeping the "Yahoo! (partial)" rule enabled) fixes this. I don't see the same issue in Chrome running the same rules and HTTPS Everywhere 2014.9.11 (which seems current?).

Ooops


Your registration was successful.

However, we couldn't log you in automatically because it looks like you don't have cookies enabled.

There are a few options:

    Clear your existing Flickr cookies
    Check that your cookies are actually enabled (Click here for instructions on how to enable your cookies.)
    If you've done both of these things, and restarted your browser, and tried to log in and it's still not working, please contact us.

Here's a link to the login page.

Activity

  1. BillWeiss commented on Nov 11, 2014

    @BillWeiss
    Author

    Also, let me know what I can add to this, I know it's a pretty sparse report.

  2. tedd4u commented on Nov 12, 2014

    @tedd4u

    Hi @BillWeiss & @2d1 - I hope I can help. Can you point me to the specific version of the rules that seem to trigger this problem? I'm sorry I am not familiar enough with this to find them on my own.

  3. BillWeiss commented on Nov 13, 2014

    @BillWeiss
    Author

    Probably important: this is with FF 33.1.

  4. jsha commented on Dec 2, 2014

    @jsha
    Member

    Excellent, thanks for finding the better fix, and sorry I duplicated some of your work.

  5. l0b0 commented on Mar 19, 2015

    @l0b0
    Contributor

    Seems like this is still an issue - I'm still getting the same message as OP with Firefox 36.0.1. Tried various privacy settings (including setting them to the default "Remember history"), clearing cache and cookies, restarting and even rebooting, but nothing worked until I disabled HTTPS Everywhere. Or has the fix not yet been released?

  6. jsha commented on Mar 19, 2015

    @jsha
    Member

    The fix is released in the latest 5.0development.3, a candidate to become the next stable version. If you'd like to try it out, please do! https://eff.org/https-everywhere/#install-development

  7. danfournier commented on Apr 30, 2015

    @danfournier

    FF 37.0.2 with SSL Everywhere 5.0.3 still seems to behave the same way?

  8. jsha commented on Apr 30, 2015

    @jsha
    Member

    @2d1 can you look at this?

  9. reopened this on Apr 30, 2015
  10. jschauma commented on Oct 10, 2015

    @jschauma

    This appears to still be an issue in https-everywhere 5.1.1 with Firefox 41.0.1 and Chrome 45.0.2454.101. See also: https://twitter.com/xor/status/652856846462660612

  11. diracdeltas commented on Oct 14, 2015

    @diracdeltas
    Contributor

    I can't seem to repro this in Chrome 46.0.2490.71 or FF 41.0.1 with 5.1.1 (OSX) so maybe it's an edge case. Can someone who has this problem verify that disabling the Flickr rule (as opposed to Yahoo) fixes this?

  12. Bisaloo commented on Mar 6, 2016

    @Bisaloo
    Collaborator

    Ok, that's strange. I can reproduce in FF 44.0.2 (Ubuntu 14.04) but not in Chromium 48.0.2564.116

    I thought it may be due to another add-on (like privacy badger) but everything works fine when I disable the Flickr.com rule.

  13. J0WI commented on May 11, 2016

    @J0WI
    Contributor

    This should be fixed in #1577

  14. Bisaloo commented on May 12, 2016

    @Bisaloo
    Collaborator

    Not fixed in FF 46.0 and HTTPSE 5.1.9

  15. reopened this on May 12, 2016
  16. J0WI commented on May 14, 2016

    @J0WI
    Contributor

    @Balgden could you compare what cookies are set with and without a secure flag, once with HTTPS Everywhere enabled and once disabled?

    Please tell us the difference (watch out that you leak no sensitive information).

  17. Balgden commented on May 16, 2016

    @Balgden
    Contributor

    @J0WI: Since I have no idea what this is about, I don't think you wanted to ping me.

  18. J0WI commented on May 16, 2016

    @J0WI
    Contributor

    Sorry, wrong auto completion. I ment @Bisaloo

  19. Bisaloo commented on May 17, 2016

    @Bisaloo
    Collaborator

    List of cookies created with the rule enabled:

    • BX
    • current_identity
    • ffs
    • flrb
    • flrbcr
    • flrbgdrp
    • flrbgmrp
    • flrbgrp
    • flrbp
    • flrbrst
    • flrbs
    • flrtags
    • localization
    • xb

    All of them are secure at the exclusion of current_identity.

    None of them is secure with the rule disabled.

  20. removed this from the Before the Next Release milestone on May 17, 2016
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