4 ms·

> 70% of security bugs are memory safety issues. That's a lot of real problems. Run your code in a WASM sandbox or on a GPU, problem solved.

by dxhdr 4y ago

adgjlsfhk1 4y ago
"Run your code in a WASM sandbox" and then your C++ is way slower (and speed is the only reason you were using C++ in the first place)
- xmcqdpt2 4y ago
  C++ compiled to wasm is just java with extra steps.
  - LeFantome 4y ago
    I totally agree but there are two differences: - WASM will be available even more places than the JVM - way more languages will target WASM than ever did the JVM Personally, I cannot wait for a WASM future. Being able to target WASM for the 90% of apps that it is fast enough for and being able to use the same language and libraries to target native when required….is going to be awesome. I really like the CLR. A more widely adopted version of something similar ( WASM ) is attractive.
    - pjmlp 4y ago
      https://en.wikipedia.org/wiki/List_of_JVM_languages https://en.wikipedia.org/wiki/List_of_JVM_languages https://en.wikipedia.org/wiki/List_of_Java_virtual_machines https://en.wikipedia.org/wiki/List_of_Java_virtual_machines https://en.wikipedia.org/wiki/List_of_CLI_languages https://en.wikipedia.org/wiki/List_of_CLI_languages And this ignoring all the bytecode environments that have existed since the 1960's.
iudqnolq 4y ago
Unless you write software that processes input from one user while having data private to another user in memory. So ... quite a lot of software
- josefx 4y ago
  Which is quite risky even with memory safe languages, if the big exploits in the last decades had anything to show it is that both RAM and CPU can be abused into bypassing any protections in place.
rng_civ 4y ago
> Run your code in a WASM sandbox Assuming your WASM sandbox is airtight, that would work. But there are still ways to break out or cause damage because within the sandbox, its like a flat address space with 0 modern protections like ASLR, stack canaries, page protection, etc. (unless you manually compile it in yourself). See [0] * [0]: https://www.usenix.org/conference/usenixsecurity20/presentation/lehmann https://www.usenix.org/conference/usenixsecurity20/presentat...
chlorion 4y ago
There is a lot of code that can't run in a WASM sandbox, like drivers for example. I do think more things running in WASM or WASM-like VM's could help a lot, but I'm not sure what the GPU part is supposed to mean.

> 70% of security bugs are memory safety issues. That's a lot of real problems. Run your code in a WASM sandbox or on a GPU, problem solved.

by dxhdr 4y ago

> 70% of security bugs are memory safety issues. That's a lot of real problems. Run your code in a WASM sandbox or on a GPU, problem solved.

adgjlsfhk1 4y ago

"Run your code in a WASM sandbox" and then your C++ is way slower (and speed is the only reason you were using C++ in the first place)

xmcqdpt2 4y ago
C++ compiled to wasm is just java with extra steps.
- LeFantome 4y ago
  I totally agree but there are two differences: - WASM will be available even more places than the JVM - way more languages will target WASM than ever did the JVM Personally, I cannot wait for a WASM future. Being able to target WASM for the 90% of apps that it is fast enough for and being able to use the same language and libraries to target native when required….is going to be awesome. I really like the CLR. A more widely adopted version of something similar ( WASM ) is attractive.
  - pjmlp 4y ago
    https://en.wikipedia.org/wiki/List_of_JVM_languages https://en.wikipedia.org/wiki/List_of_JVM_languages https://en.wikipedia.org/wiki/List_of_Java_virtual_machines https://en.wikipedia.org/wiki/List_of_Java_virtual_machines https://en.wikipedia.org/wiki/List_of_CLI_languages https://en.wikipedia.org/wiki/List_of_CLI_languages And this ignoring all the bytecode environments that have existed since the 1960's.

iudqnolq 4y ago

Unless you write software that processes input from one user while having data private to another user in memory. So ... quite a lot of software

josefx 4y ago
Which is quite risky even with memory safe languages, if the big exploits in the last decades had anything to show it is that both RAM and CPU can be abused into bypassing any protections in place.

rng_civ 4y ago

> Run your code in a WASM sandbox Assuming your WASM sandbox is airtight, that would work. But there are still ways to break out or cause damage because within the sandbox, its like a flat address space with 0 modern protections like ASLR, stack canaries, page protection, etc. (unless you manually compile it in yourself). See [0] * [0]: https://www.usenix.org/conference/usenixsecurity20/presentation/lehmann https://www.usenix.org/conference/usenixsecurity20/presentat...

chlorion 4y ago

There is a lot of code that can't run in a WASM sandbox, like drivers for example. I do think more things running in WASM or WASM-like VM's could help a lot, but I'm not sure what the GPU part is supposed to mean.