New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Installation/repair fails if we enforce hashes #843
Comments
Interesting! I can definitely verify that this is happening. Do you know where I can find more documentation on this feature so I can figure out what's going on here? This is also true of HTTPS Everywhere, I suspect it has something to do with our release process. |
Same issue in HTTPS Everywhere: EFForg/https-everywhere#5874 |
I'm hitting this on 53.0.2785.57 even if I have |
@cooperq So, in the meantime, new users like me are unable to install right? Should priority of this ticket be raised to blocker? Any solution involving disabling chrome://flags/#extension-content-verification -> Enforce strict seems like a bad idea.... |
Related to #901 |
Fixed as of 731b76a |
re-opening this since it is still an issue and we still have a workaround in place. We should figure out the right way to solve this. cc @ghostwords |
This no longer appears to be an issue. |
Hello!
chrome://flags/#extension-content-verification -> Enforce strict (hard fail if we can't get hashes)
If you have this setting Privacy Badger won't be able to be installed or repaired.
The text was updated successfully, but these errors were encountered: