4 ms·
WASM is a binary and a text format. You can turn any WASM binary to the text format and have a readable version of the blob. Firefox can automatically show you
by maeln 7y ago
WASM is a binary and a text format. You can turn any WASM binary to the text format and have a readable version of the blob. Firefox can automatically show you the text version of a WASM blob.
So no, there is no difference with a minified JS. Just because there are in a text format don't make them any more easy to reverse engineer.
- strictnein 7y agoUnless I'm completely missing something the "text version" you're talking about is just WASM and there's quite a difference between that and minified JS. ex: end $label121 get_local $var7 get_local $var9 call $func3444 get_local $var7 call $func1500
- maeln 7y agoYes this is what I am talking about. Once you know the instruction, I fail to see how it is more difficult to understand than javascript.
- strictnein 7y agoThat certainly is a take.
- CivBase 7y agoThat's like saying x86_64 assembly is as easy to understand as C. High level languages exist to make code easier to understand.
- int_19h 7y agowasm is higher-level than x86 (or any other native) assembly.
- coolreader18 7y agoHow is that any more readable than deobfuscated js? func1500(func3444(var7, var9), var7) or more likely: gw(kl(s,i),s)
- azakai 7y agoThere is a difference in degree, though. Unminified JS is usually easier to read than wasm text, in general. One practical factor: I often debug wasm files by compiling them to JS first. At least wasm has structured control flow, which helps a lot. I wish wasm had even more readability features, personally.