3 ms·

Are you saying webasm will crash or that it is insecure? These are two different things and you seem to be conflating them. In your posts you have said that i

Are you saying webasm will crash or that it is insecure? These are two different things and you seem to be conflating them. In your posts you have said that it is insecure but when you talk about specifics it just seems to be about crashing. Then when pressed you avoid any examples.

pjmlp 7y ago
I keep telling the examples, memory corruption, typical C exploits. Apparently the force is strong with WebAssembly advocacy.
- BubRoss 7y ago
  I meant working examples. Saying "it's insecure!" and then calling your own words evidence doesn't count. If there are actual exploits or security flaws, then demonstrate them with a working implementation. You seem to be trying to turn a technical discussion into an emotional one.
  - pjmlp 7y ago
    If you want code examples, just go to the CVE database and compile any memory corruption related to C into a WebAssembly module. Why should I need to provide new examples when we have plenty to chose from?
- afiori 7y ago
  internal memory corruption is different from external memory corruption.
  - pjmlp 7y ago
    It still gets a CVE award in the end.
    - afiori 7y ago
      But they are addressed differently; in particular internal memory corruption is hard to address from a framework perspective, while external memory corruption can be almost entirely eliminated.