|
@kayseesee | |||||
|
Running libFuzzer in a browser, via WASM.
We need to go deeper (?)
github.com/jonathanmetzma…
|
||||||
|
||||||
|
|
Dominik
@domenuk
|
14. pro |
|
This is pretty cool and leaves an additional thought: Could the wasm vm be used to add instrumentation to a precompiled wasm bytecode thingy? 🤔
|
||
|
|
||
|
Niklas B
@_niklasb
|
14. pro |
|
I’m pretty sure the answer is yes for most modern JS engines, just need to add instrumentation to the bytecode before JIT
|
||
|
|
||
|
opdroid1234
@opdroid1234
|
13. pro |
|
Browser is running inside a bellard.org/jslinux/ linux instance running in a table inside another browser. The outer browser is running in a cloud vm.
|
||
|
|
||
|
Jonathan Metzman
@metzmanj
|
13. pro |
|
syzkaller fuzzing jslinux was one of the first suggested improvements I got
|
||
|
|
||