-
Notifications
You must be signed in to change notification settings - Fork 5k
Make mono
CSP Compliant
#59416
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
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsWhilst investigating improving CSP compliance in Blazor, I found that Blazor WASM requires runtime/src/mono/wasm/runtime/library_mono.js Line 745 in 96cb482
This issue is to examine feasibility of removing this dependency on For reference, I found this article to be helpful for understanding CSP peculiarities (eval section).
|
A naive search shows that /cc @thaystg |
Tagging subscribers to this area: @thaystg Issue DetailsWhilst investigating improving CSP compliance in Blazor, I found that Blazor WASM requires runtime/src/mono/wasm/runtime/library_mono.js Line 745 in 96cb482
This issue is to examine feasibility of removing this dependency on For reference, I found this article to be helpful for understanding CSP peculiarities (eval section).
|
we could actually make the proxy inject the support methods and save some space |
@TanayParikh , it is great you out there are working on CSP cleanup. |
this is gone in main |
Assuming this is for 7.0? |
yes |
Whilst investigating improving CSP compliance in Blazor, I found that Blazor WASM requires
unsafe-eval
due to mono's usage ofeval
:runtime/src/mono/wasm/runtime/library_mono.js
Line 745 in 96cb482
This issue is to examine feasibility of removing this dependency on
eval
so thatunsafe-eval
is no longer required in the Blazor WASM CSP.For reference, I found this article to be helpful for understanding CSP peculiarities (eval section).
The text was updated successfully, but these errors were encountered: