Depends on the definition of "security problem", WASM only protects from a small (but important) subset.
In general, WASM gives you about the same security guarantees as Javascript, it runs your code inside a sandbox that protects the "outside" of the sandbox from what's happening inside. You'll still be able to create and enjoy the whole range of memory corruption problems and crashes C/C++ has to offer, but those are contained *inside* the sandbox, they cannot be used to "escape" and cause harm outside the sandbox (unless the sandbox implementation has bugs, or nasty hardware surprises show up, like Rowhammer/Spectre/Meltdown). What WASM can't protect from is "non-technical" security issues like stealing passwords or other secrets through fishing / social engineering of course. Cheers, -Floh. On Monday, 11 March 2019 09:08:16 UTC+1, ssssss1 wrote: > > Hello > I read that the c/c++ code have security issues but i will want to know if > i convert the c/c++ code to wasm code using emscripten the security > problem will be eliminate or not ? > Thanks in advance. > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
