3 ms·
Maybe OT, but does anyone know if there is runtime analysis of JS and/or wasm? Obfuscation is a serious threat to the open web, and things like fingerprinting
by klabb3 3y ago
Maybe OT, but does anyone know if there is runtime analysis of JS and/or wasm?
Obfuscation is a serious threat to the open web, and things like fingerprinting can be incredibly invasive.
Web browsers typically only support static “prettifying” (ie auto indent). I’ve seen websites probe for chrome extensions, canvas and all kinds of APIs. Deobfuscators are often not enough to restore legibility. (I assume disassemblers are similar, but I’ve never tried.)
I would love to have a trace/intercept/breakpoints of any external APIs called in order to restore a sense of control over what code websites run. Ideally, integrated in the browser. With WASM gaining popularity, this will become (much) more important, imo.