3 ms·
Wouldn't dependency hijacking only be an issue during build/packaging, rather than installation when everything is frozen? All you're going to see as an end-use
by maven29 4y ago
Wouldn't dependency hijacking only be an issue during build/packaging, rather than installation when everything is frozen? All you're going to see as an end-user is a prebuilt binary that doesn't even know what NPM is. Again, this is no different from native apps.
Native apps are objectively worse than WASM in terms of security/privacy risks as they have access to all userspace syscalls. It's not like WASM bytecode can link against system libraries. Everything has to go through the browser/runtime sandbox. The only real risk here is side-channel attacks like Meltdown.
- encryptluks2 4y agoAgain though, they are already sandbox frameworks for the desktop for native apps. There is not a need to have the web browser, a notoriously anti-privacy component, as a DRM player for non-DRM content.