Privacybadger: PB is blocking auth0-lock

[luisrudge]

Hi. I'm Luis from auth0. Privacy Badger is blocking our CDN and we had a couple of users that brought that to our attention (https://github.com/auth0/lock/issues/362). How can we work together to fix this issue?

Thanks!

[mackenzieg]

+1 same issue

[ghostwords]

Hi @luisrudge, would Auth0 be able to adopt the EFF Do Not Track policy? If your company can and will abide by the policy's requirements, posting the policy on your domains will tell Privacy Badger to allow loading of resources from those domains. Let me know if you have any questions.

[luisrudge]

@ghostwords Thanks for the heads up. We'll add it to our backlog.

[LeeAtZoetik]

Same issue for me - *.auth0.com is very important for what we access

[excenter]

This is marked as closed, but I just spent a fun couple hours trying to figure out what was trapping me in a login loop, and the answer was that my-tenant.auth0.com was blocked by privacy badger.
I'd love to get more people using PB, but I can't recommend it to any of my coworkers or application users without a mini-seminar on how to un-break our app.

[bcyphers]

Hi @excenter, this issue (and the related one, #2313, which is about auth0.com), were closed because the relevant pull request was merged into master with #2314. The merge happened last week, but we haven't had a public release yet so the changes are not live on the web store. That will happen very soon.

Edit: that was wrong, sorry. As @ghostwords said below, yellowlist updates are separate from normal releases, but the yellowlist hasn't been updated since the merge, either. That will happen soon.

[ghostwords]

@bcyphers Yellowlist PRs don't require a new release.

[ArturKlajnerok]

Thanks for resolving this @bcyphers & @ghostwords 🙇. Do you know when the yellowlist update is scheduled ?

[excenter]

Thanks all, excited to see progress!

[bcyphers]

This should be fixed now: https://www.eff.org/files/cookieblocklist.txt (ctrl-F "auth0")