I’m talking about a FS2020 loophole, defeating the whole point of sandboxing 3rd party devs for security.
In other words as of today, and most likely during the lifespan of FS2020 given the nature of the loophole, you can inject a virus in FS2020 and stole customer credentials via the loophole, but 3rd party devs can’t even access the bare bone metal for faster and better add-ons.
I understand the reasons behind WASM and this is a good technology for what it is good at, but it shouldn’t be used in my opinion to make customers fearing 3rd party vendors are going to stole their personal information if they are not sandboxed thanks to Microsoft and Asobo… Otherwise in my opinion this is a fallacious argument, telling the 3rd party vendors are thieves and customers must be protected from them.
RXP GTN 750/650 and GNS 530/430 for FS2020 - Page 4 - RXP General Forum - The AVSIM Community
NB: the official transcript and the live Q&A video are pretty much similar, except for this specific question: “Can we talk about DLL?”
Live comment:
- DLLs can carry unsafe code and they can’t have unsafe code in add-ons in the Market Place. Sandboxing is good for having safe add-ons in the Microsoft store.
- Sandboxing is also a good way to port legacy addons in C++
Official transcript:
Eric – When you ship a DLL, you never know what it is going to do! It has access to personal informal information and result in having security issues. Using WASM, we are sure that 3rd party content only accesses designated files!
NB: you’ll find my other comments about this and the SDK from the link above.