Enable WebAssemblyCSP flag so wasm-eval CSP can be used instead of requiring unsafe-eval (#617)
This commit is contained in:
parent
9569a46f8a
commit
625b8b828f
|
@ -47,7 +47,7 @@ X-Frame-Options "DENY";
|
|||
```
|
||||
A working Content Security Policy looks like that:
|
||||
```
|
||||
Content-Security-Policy "img-src 'self' 'unsafe-inline' data:; style-src 'self' 'unsafe-inline'; font-src 'self'; object-src 'none'; base-uri 'self'; form-action 'none';";
|
||||
Content-Security-Policy "img-src 'self' 'unsafe-inline' data:; script-src 'self' 'unsafe-inline' 'wasm-eval'; style-src 'self' 'unsafe-inline'; font-src 'self'; object-src 'none'; base-uri 'self'; form-action 'none';";
|
||||
```
|
||||
|
||||
## Development
|
||||
|
|
2
main.js
2
main.js
|
@ -213,7 +213,7 @@ function createJitsiMeetWindow() {
|
|||
minHeight: 600,
|
||||
show: false,
|
||||
webPreferences: {
|
||||
enableBlinkFeatures: 'RTCInsertableStreams,WebAssemblySimd',
|
||||
enableBlinkFeatures: 'RTCInsertableStreams,WebAssemblySimd,WebAssemblyCSP',
|
||||
enableRemoteModule: true,
|
||||
contextIsolation: false,
|
||||
nativeWindowOpen: true,
|
||||
|
|
Loading…
Reference in New Issue