5 ms·
Where the sandbox now has a much larger attack surface as it has to implement a whole new virtual machine to run the webasm.
by chillydawg 10y ago
Where the sandbox now has a much larger attack surface as it has to implement a whole new virtual machine to run the webasm.
- gsnedders 10y agoNobody's writing a whole new VM to run it; everyone is just treating it as another input format to their JS VM.
- icefox 10y agohttps://github.com/AndrewScheidecker/WAVM https://github.com/AndrewScheidecker/WAVM
- gsnedders 10y agoGiven the context, what browser is that going into? How is that relevant to browser sandboxing?
- icefox 10y agoAh yes within the browser space the various companies are just putting web assembly in/alongside the existing javascript engines. WAVM was just an example of a whole new vm that isn't for a browser, but does run webassembly.
- gsnedders 10y agoYeah; I probably should've been more explicit in my original comment: there's definitely new VMs being written for WASM, but none are currently expecting to go into browsers, hence concerns about sandbox escapes from browsers aren't affected by them.