Skip to content
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

Add 'wasm-unsafe-eval' to custom CSP (fix #906) #907

Merged
merged 1 commit into from
Jul 10, 2022

Conversation

mozfreddyb
Copy link
Contributor

It seems that some dependencies (at least argon2-browser) require allowing WebAssembly at the CSP level.
Recent Firefox allows that by default, but having your own CSP means this extension won't be able to benefit from this automatically.

It seems that some dependencies (at least argon2-browser) require allowing WebAssembly at the CSP level.
Recent Firefox allows that by default, but having your own CSP means this extension won't be able to benefit from this automatically.
@mozfreddyb
Copy link
Contributor Author

FWIW, I do not intend to do more work on this pull request. Feel free to steal / adjust and merge at your own convenient. :)

@mymindstorm
Copy link
Member

mymindstorm commented Jul 10, 2022

Thanks for this! Although, it seems that MV2 extensions are not affected by this just yet per bug 1770909

@mymindstorm mymindstorm merged commit d34f98b into Authenticator-Extension:dev Jul 10, 2022
@mozfreddyb
Copy link
Contributor Author

Indeed, we changed course after we learned that it would impact too many add-ons.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants