Privacybadger: Privacy Badger broken on Chrome Dev

[ajthemacboy]

Privacy Badger is reported as 'corrupt' on Chrome Dev (my exact version was 54.0.2837.0 dev-m (64 bit)) but works fine on the stable channel. I've tested on two different browsers. I have not tested the Beta or Canary channels. Clicking "Repair" reinstalls the extension with the same error.

This does not occur with any other extensions.

This occurs even when "Extension content verification" is set to Bootstrap in chrome://flags.

This issue also occurs with HTTPS Everywhere and has been reported on its GitHub as well.

[cowlicks]

I can reproduce this.

[cowlicks]

I suppose this could be the problem, from this chrome issue:

... downloading additional files to use in the extension that are placed in some new place should be fully supported. But self-modification of files that came in the original .crx cannot be.

[cowlicks]

I can't find a way to debug this so it's pretty opaque.

Privacy Badger does not use the filesystem api so I don't see how it could be changing its own files (which causes the issue in my last comment).

I don't think it is this zero length files bug because I couldn't find any zero length files.

https://bugs.chromium.org/p/chromium/issues/detail?id=399251#makechanges

[cowlicks]

Maybe we are violating the default Content Security Policy we get by having "manifest_version": 2. I'm not even sure if this would cause the error we are seeing though. Basically we:

• Can't use eval (but I don't think we do)
• Can't use inline js (but I don't think we do)
• Can only use local scripts, and object resources. (I think we do this)

But these rules don't apply to content scripts. Maybe I missed something.

[ajthemacboy]

See https://github.com/EFForg/https-everywhere/issues/5874

[josh-berry]

I am seeing this in Chrome Beta as well (53.0.2785.80 beta (64-bit)), on MacOS El Capitan (10.11.6), with Privacy Badger 2016.08.29.

Notably, I do NOT see the same issue with HTTPS Everywhere.

[cooperq]

We have a fix for this now which will be in the next release. For now
you can go to chrome://flags and find the setting for 'extension content
verification' and change it from 'enforce strict' to 'enforce'. You then
can uninstall and reinstall the extension and it should be fixed. Once
the fix is released you should be able to change it back.
This is now fixed as of 731b76a80c88d029430540097a5a6e347a081eda

[MikeN123]

Setting extension content verification to 'enforce' unfortunately doesn't fix the issue for me.

[cooperq]

So it turns out this is an issue in chrome, the chrome devs are aware of it and are working on a fix now. Follow the issue here: https://bugs.chromium.org/p/chromium/issues/detail?id=643814