3 ms·
>CNAME uncloaking is essential >Chrome doesn't have an API for that. It rolled out a year ago. https://bugs.chromium.org/p/chromium/issues/detail?id=1151047
by charcircuit 4y ago
>CNAME uncloaking is essential
>Chrome doesn't have an API for that.
It rolled out a year ago.
https://bugs.chromium.org/p/chromium/issues/detail?id=1151047 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.
- postalrat 4y agoLoading remote wasm after installing should be allowed. Your extension would still need bindings in javascript for whatever the wasm is doing.
- charcircuit 4y agoJust knowing the bindings isn't enough to be able to classify a wasm file as being malicious.
- rasz 4y ago>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.
- charcircuit 4y agoHow 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.