Re:uBlock 1.48.0 Adds Readiness Status, Code Viewer, and Oth...
by postalrat on Wednesday March 22, 2023 @12:01AM
(#35256664)
Loading remote wasm after installing should be allowed. Your extension would still need bindings in javascript for whatever the wasm is doing.
Re:uBlock 1.48.0 Adds Readiness Status, Code Viewer, and Oth...
by charcircuit on Wednesday March 22, 2023 @01:23AM
(#35257148)
Just knowing the bindings isn't enough to be able to classify a wasm file as being malicious.
Re:uBlock 1.48.0 Adds Readiness Status, Code Viewer, and Oth...
by rasz on Wednesday March 22, 2023 @12:26AM
(#35256825)
>remote javascript
When Google says "remote" they really mean "remote to Google". You cant execute any of your own code from local drive, everything must be controlled by Google.
Re:uBlock 1.48.0 Adds Readiness Status, Code Viewer, and Oth...
by charcircuit on Wednesday March 22, 2023 @01:34AM
(#35257208)
How can a malware scan be effective if all the code can't be scanned? Imagine if antimalware only scanned exe files and ignored dll files.
>Chrome doesn't have an API for that.
It rolled out a year ago.
https://bugs.chromium.org/p/chromium/issues/detail?id=115104...
>Chrome because Chrome doesn't allow extensions to use wasm.
Chrome doesn't allow loading remote web assembly in mv3 extentions. You can't run remote javascript either. It's fine if you bundle the wasm with your extension.