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

Correct error if wasm for BLS signature verification can't be instantiated #686

Open
domwoe opened this issue Feb 12, 2023 · 0 comments
Open

Comments

@domwoe
Copy link
Member

domwoe commented Feb 12, 2023

Currently, an error thrown by the BLS verification gets caught and a very generic Signature verification failed is thrown. In most cases, the reason for failure is that the IC public key is used though the message is signed by the local replica. However, in my case, a CSP directive prevented the loading of the wasm, but since this error was caught it took me quite a while to discover this reason:

CompileError: WebAssembly.instantiate(): Refused to compile or instantiate WebAssembly module because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive: "script-src 'self' https://www.google-analytics.com https://www.googletagmanager.com 'unsafe-inline'"

It would be great if we would distinguish between this error and the typical failure to verify the signature.

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

No branches or pull requests

1 participant