Re: Documenting the ENABLE_WASM flag for chrome

2022-06-01 Thread Stuart Henderson
On 2022/06/02 04:17, Yifei Zhan wrote: > > +WebAssemble: > + > +- some websites require WebAssemble to be functional, this will appear in > +the JavaScript console as the following error: > + > + Uncaught (in promise) ReferenceError: WebAssembly is not defined > + > +- WebAssemble is disabled by

Re: Documenting the ENABLE_WASM flag for chrome

2022-06-02 Thread Sebastien Marie
On Thu, Jun 02, 2022 at 07:55:16AM +0100, Stuart Henderson wrote: > On 2022/06/02 04:17, Yifei Zhan wrote: > > > > +WebAssemble: > > + > > +- some websites require WebAssemble to be functional, this will appear in > > +the JavaScript console as the following error: > > + > > + Uncaught (in promi

Re: Documenting the ENABLE_WASM flag for chrome

2022-06-02 Thread Theo de Raadt
My take on this is that WASM is quite simply just new attack surface. Hear me out. Imagine tomorrow someone invents WebX86. One website uses it. Support arrives for browsers, now 10 websites use it. So it gets added. And next year, someone inventest webARM64thingy. One website uses it. Supp

Re: Documenting the ENABLE_WASM flag for chrome

2022-06-04 Thread Theo de Raadt
Yifei Zhan wrote: > > WASM is not required on the open internet. Not required Today. Hopefully > > never. > > I think we unfortunately now already live in such a world, both > BigBlueButton and jitsi make use of WASM, and BigBlueButton won't let > me join a meeting without having WASM enabl