Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Wasm has a pretty simple execution model, wouldn’t be hard to write something that preprocesses wasm code during load, similar to what you can do with java classloaders.


We can handle Wasm like Flash: declare it obsolete and then reinvent it again.


Declaring something obsolete doesn't make it so. Flash went away because of iPhone and rise of mobile app and still it took about a decade for it to be irrelevant. Without a similar tectonic shift, it would take longer.


Easily preventable using encrypted wasm modules.


I don't think WASM can write to its code memory to self-decrypt. At some point, the WASM has to create a DOM node containing the decrypted script, at which point you can process the code.


Now that is an idea for a prof of concept.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: