I read some parts of the spec of WebAssembly recently, and there were several things that disappointed me. To name a few: 1) There is no way to allocate in a function's variable stack continuous memory space that spans…
From my experiences of reversing Windows x86 applications, I don't think WebAssembly has a greater capacity for obfuscation. In fact, I think WebAssembly is less capable of obfuscating code than JavaScript. It is…
According to the paper, they seem to have modified Chromium's JavaScript engine in order to record execution paths of JavaScript code. Does anyone know exactly how they modified Chromium (or preferably the exact patch…
I read some parts of the spec of WebAssembly recently, and there were several things that disappointed me. To name a few: 1) There is no way to allocate in a function's variable stack continuous memory space that spans…
From my experiences of reversing Windows x86 applications, I don't think WebAssembly has a greater capacity for obfuscation. In fact, I think WebAssembly is less capable of obfuscating code than JavaScript. It is…
According to the paper, they seem to have modified Chromium's JavaScript engine in order to record execution paths of JavaScript code. Does anyone know exactly how they modified Chromium (or preferably the exact patch…